when installing systemd, it creates /run/nologin preventing all users from logging in.

Bug #1650634 reported by tim.tadh
30
This bug affects 7 people
Affects Status Importance Assigned to Milestone
systemd
New
Unknown
systemd (Suse)
Unknown
Unknown
systemd (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

How to replicate:

sudo apt-get install systemd

wait for 5 minutes

check to see if /run/nologin appears. If it does the bug is present. See https://ubuntuforums.org/showthread.php?t=2327330

I ran this command via ansible on all of my servers. Then I could no longer log into any of them. Pretty big bug in my opinion. Please fix.

-Tim

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: systemd 204-5ubuntu20.20
ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
Uname: Linux 3.13.0-105-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Dec 16 12:03:55 2016
InstallationDate: Installed on 2014-04-21 (970 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
tim.tadh (tim-tadh) wrote :
Changed in systemd:
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Mikhail Novosyolov (mikhailnov) wrote :

Thank you, today my Ubuntu 16.04 booted into the maintenance mode and systemctl --failed showed only nfs-resolvd.service. I made
# systemctl restart ssh
then I got:
"System is booting up. See pam_nologin(8)"
Authentication failed.

# rm -fv /run/nologin
solved the issue.

I ran
# apt install --reinstall systemd
and /run/nologin did not appear again.

Revision history for this message
Mikhail Novosyolov (mikhailnov) wrote :

I got this again.
Commented out the line
auth requisite pam_nologin.so
in /etc/pam.d/login

Now /run/nologin must be ignored and do not prevent the system from booting up correctly, but this bug must be marked as CRITICAL, I think.

Revision history for this message
Graham Leggett (minfrin-y) wrote :

Deploy Ubuntu Bionic machine from AWS, try and log in:

"System is booting up. See pam_nologin(8)"

Given it is impossible to log in, it's impossible to see what's wrong, or fix it.

Revision history for this message
Maris Nartiss (maris-nartiss) wrote :

Graham, you could be hit by a different bug. (In my case it was fubared NFS mount from fstab – turns out NFS mounts should be removed from fstab before upgrades) You are interested in solving "pam_nologin should allow sudoers to log in" – it is bug #1847902

Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.