FS#39207 - [systemd] pam_systemd timeout failure when logging in
Attached to Project:
Arch Linux
Opened by Greg KH (gregkh) - Friday, 07 March 2014, 00:04 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 11 March 2014, 15:27 GMT
Opened by Greg KH (gregkh) - Friday, 07 March 2014, 00:04 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 11 March 2014, 15:27 GMT
|
Details
When logging into a box through ssh, I get the following 30
second delay and error log messages:
Mar 06 23:59:18 eudyptula sshd[27670]: pam_unix(sshd:session): session opened for user gregkh by (uid=0) Mar 06 23:59:43 eudyptula sshd[27670]: pam_systemd(sshd:session): Failed to create session: Connection timed out Mar 06 23:59:43 eudyptula dbus[2288]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Mar 06 23:59:43 eudyptula systemd-logind[2287]: Failed to start session scope session-107.scope: Activation of org.freedesktop.systemd1 timed out org.freedesktop.DBus.Error.TimedOut And then the login session happens This is systemd 210, and yes, the system has been rebooted. A 30 second delay of logging in is a pain when doing remote commands over ssh (like git pulls/pushes) |
This task depends upon
Closed by Dave Reisner (falconindy)
Tuesday, 11 March 2014, 15:27 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 210-3
Tuesday, 11 March 2014, 15:27 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 210-3
What did you "fix" that solves these issues, some patches from upstream?
I'm going to leave this open until systemd hits [core] since this seems to have been mentioned a number of times on the forums an on IRC.
I noticed "HOSTNAME login: [3251250.699856] systemd[1]: segfault at 1050 ip 0000000000001050 sp 00007fffc3c0ed28 error 14 in systemd[400000+106000]" when rebooting though but that's probably linked with recent kernel update.
I'm on 3.13.5-1-ARCH, x86_64.