You are not logged in.
Hi all,
I cannot login as a simple user after the update of systemd to version 214-2 on my laptop. The error message says "System is booting up. See pam_nologin(8)". However, login as root is possible and su to another user afterward is also possible. Downgrading to systemd to 213-9 fixes the issue. Erasing completely /etc/pam.d and reinstalling pam and pambase allows me to login again, even with systemd 214-2. So I then tried to re-install the packages I have that own files in /etc/pam.d:
shadow
util-linux
cronie
cups
i3lock
kdebase-workspace
polkit
postgresql
inetutils
samba
openssh
systemdBut then, I am unable to login again. I guess I should try to install each of these one after another in order to locate the one that is causing problems but if someone could maybe install all of these packages and tel me if he then is also unable to login, this could help for concluding that this is a reproducible bug or that it is only on this machine.
By the way, this is the list of files I have in /etc/pam.d:
total 148K
-rw-r--r-- 1 root root 160 May 10 15:23 chage
-rw-r--r-- 1 root root 160 Apr 24 15:43 chfn
-rw-r--r-- 1 root root 103 May 10 15:23 chgpasswd
-rw-r--r-- 1 root root 174 May 10 15:23 chpasswd
-rw-r--r-- 1 root root 160 Apr 24 15:43 chsh
-rw-r--r-- 1 root root 281 Apr 13 09:59 crond
-rw-r--r-- 1 root root 87 May 31 12:05 cups
-rw-r--r-- 1 root root 160 May 10 15:23 groupadd
-rw-r--r-- 1 root root 160 May 10 15:23 groupdel
-rw-r--r-- 1 root root 103 May 10 15:23 groupmems
-rw-r--r-- 1 root root 160 May 10 15:23 groupmod
-rw-r--r-- 1 root root 171 Jul 12 2013 i3lock
-rw-r--r-- 1 root root 134 Jun 24 18:50 kde
-rw-r--r-- 1 root root 297 Jun 24 18:50 kde-np
-rw-r--r-- 1 root root 55 Jun 24 18:50 kscreensaver
-rw-r--r-- 1 root root 220 Apr 24 15:43 login
-rw-r--r-- 1 root root 174 May 10 15:23 newusers
-rw-r--r-- 1 root root 127 Sep 28 2013 other
-rw-r--r-- 1 root root 198 May 10 15:23 passwd
-rw-r--r-- 1 root root 312 Feb 25 15:36 polkit-1
-rw-r--r-- 1 root root 87 May 31 08:23 postgresql
-rw-r--r-- 1 root root 500 Jan 14 22:05 rlogin
-rw-r--r-- 1 root root 425 Jan 14 22:05 rsh
-rw-r--r-- 1 root root 87 Jun 23 15:03 samba
-rw-r--r-- 1 root root 160 May 10 15:23 shadow
-rw-r--r-- 1 root root 232 Apr 20 21:36 sshd
-rw-r--r-- 1 root root 366 Apr 24 15:43 su
-rw-r--r-- 1 root root 366 Apr 24 15:43 su-l
-rw-r--r-- 1 root root 441 Sep 28 2013 system-auth
-rw-r--r-- 1 root root 143 Sep 28 2013 system-local-login
-rw-r--r-- 1 root root 619 Sep 28 2013 system-login
-rw-r--r-- 1 root root 143 Sep 28 2013 system-remote-login
-rw-r--r-- 1 root root 260 Sep 28 2013 system-services
-rw-r--r-- 1 root root 183 Jun 14 14:56 systemd-user
-rw-r--r-- 1 root root 160 May 10 15:23 useradd
-rw-r--r-- 1 root root 160 May 10 15:23 userdel
-rw-r--r-- 1 root root 160 May 10 15:23 usermodAny help is appreciated.
Last edited by Rolinh (2014-07-14 09:51:13)
Offline
Do you have any failed services when this happens? Is systemd-user-sessions.service running happily? 214-2 has been out there for a week or so, depending on your mirror, of course, but it's running fine here.
Also: there were a bunch of changes in /etc/passwd and /etc/shadow recently. Did you merge all your pacnew changes?
Offline
if someone could maybe install all of these packages and tel me if he then is also unable to login
I have the same packages installed except for kdebase-workspace. If your graphical login fails, this is likely the culprit. The different files in pam.d allow different programs to authenticate users. su uses /etc/pam.d/su, and so on for others. As su works for you, this looks like a KDE-only problem to me. You could try to log in remotely via ssh and on the text terminal screens (may be hard to get at with default X11 config) to ascertain this.
Officer, I had to drive home - I was way too drunk to teleport!
Offline
Sorry for the lack of answers here. I pretty much did not update my laptop since then until today and, after the ~220 pkg updates and the merging of the pacnew files (especially those from filesystem package update => /etc/group and gshadow) and a reboot, all went back into normal.
But just to answer your questions:
@twelveeighty: I had no service failure when this happens (and it happened always, it was not random btw). And yes, I had merged all the pacnew files. I'm pretty meticulous when it comes to this.
@deepsoul: This was not only the graphical login that was failing. I could not login from ssh or console either (except as root from the console and then su to a user as I have explained in my first post but sorry, I did not give the precision that I used the console).
Anyway, thanks for your help guys.
Offline