Re: Strange message on boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Feb 11, 2024, at 12:38, Robert McBroom via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
On 2/11/24 10:30, Jonathan Billings wrote:
On Feb 10, 2024, at 19:05, Robert McBroom via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
I typically boot in mode 3 to a terminal. Fedora f39 going to lxde as the desktop. Today with a cold boot and entering  the user login the following message showed

--

System is going down. Unprivileged users are not permitted to log in anymore , for technical details see pam_nologin(8)

--

Further messages indicated that some updates were being installed. After some minutes the system rebooted.

Everything known has been done to prevent any automatic updates with manual dnf being used as needed. The pam_login module looks for the existence of

/etc/nologin or

/var/run/nolongin

What is updating files without a command  and writing these entries?
You mentioned you disabled DNF auto updates, but is the packagekit-offline-updates.service unit running?  That can also perform updates (via PackageKit->dnf) and reboot.  Perhaps the login shell was somehow added to the system-update.target?

It’s worth looking at the journal at that time to see what was running.  This isn’t a completely unsolvable mystery, all the actions will be in the journal.
]# systemctl status packagekit
○ packagekit.service - PackageKit Daemon
    Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
   Drop-In: /usr/lib/systemd/system/service.d
            └─10-timeout-abort.conf
    Active: inactive (dead)

~]# systemctl status system-update.target
○ system-update.target - Offline System Update
    Loaded: loaded (/usr/lib/systemd/system/system-update.target; static)
    Active: inactive (dead)


Neither of those commands are going to tell you what happened when you encountered the reboot. I don’t even know what to expect on running a systemctl status on a *target*. 

You need to use journalctl to find the time in the journal leading up to the login and see what services were started. The “last” command should give you an idea of the timestamp. 

-- 
Jonathan Billings
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux