Arch Linux

Wey

Member

Registered: 2011-04-22

Posts: 217

[Solved] Instant logout (with systemd-38-2)?

Hello everyone,
I'm not sure if this is related to the testing-repository, but since this morning, I am unable to login. I am not using a display manager, so after boot, I enter my username and password at a tty. For a very short moment I can see the line with "Last login: ...", but then, I get logged out instantly again. It is different from typing in a wrong password, then it just waits for some seconds and says "Login incorrect...", so I'm definitely entering the right credentials.  Same for normal- and superuser. When chrooting into the system, lastlog shows the correct login dates for today.

Here is the upgrade path from my pacman.log. From my point of view, the systemd update was the only system relevant package yesterday, and the linux/udev/kmod etc. was the day before and did not cause any problems back then. (The update from today was from within the chroot).

[2012-01-12 18:43] upgraded libassuan (2.0.2-1 -> 2.0.3-1)
[2012-01-12 22:14] upgraded kmod (3-5 -> 3-6)
[2012-01-12 22:14] upgraded udev (175-1 -> 177-1)
[2012-01-13 10:55] upgraded inetutils (1.9-1 -> 1.9.1-1)
[2012-01-13 10:55] upgraded mkinitcpio (0.8.1-1 -> 0.8.2-1)
[2012-01-13 10:56] upgraded linux (3.2-2 -> 3.2.1-1)
[2012-01-13 23:05] upgraded libarchive (3.0.2-1 -> 3.0.3-2)
[2012-01-13 23:05] upgraded pacman (4.0.1-3 -> 4.0.1-4)
[2012-01-14 00:30] upgraded bluez (4.97-1 -> 4.98-1)
[2012-01-14 13:25] upgraded mpg123 (1.13.4-1 -> 1.13.4-2)
[2012-01-14 13:25] upgraded wine (1.3.36-1 -> 1.3.37-1)
[2012-01-14 15:01] upgraded gmime (2.4.31-1 -> 2.6.4-1)
[2012-01-14 15:01] upgraded totem-plparser (2.32.6-2 -> 2.32.6-3)
[2012-01-14 16:47] upgraded cower-git (20120102-1 -> 20120114-1)
[2012-01-14 23:43] upgraded systemd (38-1 -> 38-2)
[2012-01-15 12:08] upgraded vim-runtime (7.3.353-2 -> 7.3.401-1)
[2012-01-15 12:08] upgraded gvim (7.3.353-2 -> 7.3.401-1)

I am not that familiar with the systemd-logind features, but does it also handle tty logins? If so, were there any relevant changes in the -2 rebuild for the systemd-package?

Edit: I experimentally downgraded to systemd-38-1 and it works fine...

Last edited by Wey (2012-01-15 19:29:13)

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,111

Website

Re: [Solved] Instant logout (with systemd-38-2)?

systemd-logind is involved in any login that hooks up with pam_systemd.so. I'm not sure how this would be broken in 38-2, given that the only real changes were the addition of patches that touched the shutdown ordering of the syslog socket and a bugfix for tmpfiles on i686. I did also remove a ./configure flag that should have been harmless. Have you by chance rebooted since upgrading to 38-2?

I can't reproduce this, but someone else mentioned that I broke ACLs (applied by logind) with 38-2, so I'm a little concerned...

---

blog | ±github

Wey

Member

Registered: 2011-04-22

Posts: 217

Re: [Solved] Instant logout (with systemd-38-2)?

Have you by chance rebooted since upgrading to 38-2?

When running 38-1 and upgrading to 38-2, logging in stops working instantly on new ttys. This behavior persists after reboots until i downgrade from a chroot.

Here is the relevant output from the journal:

Jan 15 17:16:54 arch systemd-logind[259]: New session 2 of user root.
Jan 15 17:16:54 arch login[381]: ROOT LOGIN  on '/dev/tty2'
Jan 15 17:17:08 arch dbus-daemon[279]: dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus-daemon[279]: dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus-daemon[279]: dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus-daemon[279]: dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus-daemon[279]: dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus-daemon[279]: dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus-daemon[279]: dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus-daemon[279]: dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus[279]: [system] Reloaded configuration
Jan 15 17:17:08 arch dbus[279]: [system] Reloaded configuration
Jan 15 17:17:12 arch login[412]: [blob data]
Jan 15 17:17:12 arch login[412]: PAM adding faulty module: /lib/security/pam_systemd.so
Jan 15 17:17:15 arch login[412]: pam_unix(login:session): session opened for user felix by LOGIN(uid=0)
Jan 15 17:17:15 arch login[412]: Module is unknown
Jan 15 17:17:15 arch systemd[1]: getty@tty3.service holdoff time over, scheduling restart.

And the corresponding time frame from the pacman log:

[2012-01-15 17:16] Running 'pacman -Syu'
[2012-01-15 17:16] synchronizing package lists
[2012-01-15 17:16] starting full system upgrade
[2012-01-15 17:17] upgraded systemd (38-1 -> 38-2)

If the logs do not clear this up, I can try to compile 38-1, applying the changes to 38-2 step by step.

Wey

Member

Registered: 2011-04-22

Posts: 217

Re: [Solved] Instant logout (with systemd-38-2)?

[Solved] with systemd-38-3.