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?
On Sat, 2024-02-10 at 19:05 -0500, Robert McBroom via users wrote:
What is updating files without a command and writing these entries?
Had you done any manual updates anytime before you shutdown? Perhaps they were completing their install.
On 2/10/24 22:00, Tim wrote:
On Sat, 2024-02-10 at 19:05 -0500, Robert McBroom via users wrote:
What is updating files without a command and writing these entries?
Had you done any manual updates anytime before you shutdown? Perhaps they were completing their install.
There was plenty of time after the update. Are you saying that dnf update is not done when it is finished?
On 11 Feb 2024, at 04:07, Robert McBroom via users users@lists.fedoraproject.org wrote:
There was plenty of time after the update. Are you saying that dnf update is not done when it is finished?
Some installs trigger building kernel modules, which can only happen after dnf is finished. For example the rpmfusion nvidia driver is built by akmods that way. You can check to see if there are jobs running using:
sudo systemctl --list-jobs
Barry
On 2/11/24 05:19, Barry wrote:
On 11 Feb 2024, at 04:07, Robert McBroom via users users@lists.fedoraproject.org wrote:
There was plenty of time after the update. Are you saying that dnf update is not done when it is finished?
Some installs trigger building kernel modules, which can only happen after dnf is finished. For example the rpmfusion nvidia driver is built by akmods that way. You can check to see if there are jobs running using:
sudo systemctl --list-jobsBarry
System time out shutdown to cold boot should have cleared those rebuilds
On Sat, Feb 10, 2024 at 8:05 PM Robert McBroom via users < users@lists.fedoraproject.org> 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?
Maybe firmware updates -- these seem to differ depending on the type of device and vendor.
From https://en.wikipedia.org/wiki/Fwupd:
It [fwupd] is designed primarily for servicing the Unified Extensible https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface Firmware Interface https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface (UEFI) firmware on supported devices via EFI System Resource Table (ESRT) and UEFI Capsule, which is supported in Linux kernel https://en.wikipedia.org/wiki/Linux_kernel 4.2 and later. [...] ESRT allows the firmware to expose updatable components to the operating system, which can pass a UEFI capsule with updated firmware for processing and installation on the next boot.
Journalctl may have more details, if you can find them amid the mass of detail journalctl provides. It would be nice to have a mechanism that highlights entries that are new to the current boot but have not appeared in previous boots.
On Feb 10, 2024, at 19:05, Robert McBroom via users users@lists.fedoraproject.org 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.
On 2/11/24 10:30, Jonathan Billings wrote:
On Feb 10, 2024, at 19:05, Robert McBroom via usersusers@lists.fedoraproject.org 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)
-
Barry -
George N. White III -
Jonathan Billings -
Robert McBroom -
Tim