Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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
Comment by Dave Reisner (falconindy) - Friday, 07 March 2014, 03:23 GMT
Hrmm, I suspect that systemd has probably crashed and this is what causes the timeout (evidenced particularly by the dbus activation timeout). I pushed 210-3 into [testing] tonight which fixed at least 2 segfaults. Could you see if you can replicate the error with the new package?
Comment by Greg KH (gregkh) - Friday, 07 March 2014, 05:50 GMT
Yes, 210-3 does seem to work for me, many thanks.

What did you "fix" that solves these issues, some patches from upstream?
Comment by Dave Reisner (falconindy) - Friday, 07 March 2014, 13:41 GMT
Yes, exactly -- backport of commits marked as bugfixes.

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.
Comment by Grzegorz (gregosky) - Tuesday, 11 March 2014, 15:00 GMT
  • Field changed: Percent Complete (100% → 0%)
Update pulled from repositories (11-03-2014) does not solve this issue for me. My logs are similar, I'm getting timeouts from org.freedesktop.login1 and org.freedesktop.systemd1.
Comment by Dave Reisner (falconindy) - Tuesday, 11 March 2014, 15:04 GMT
I don't do dates. What version did you update to and have you rebooted since upgrading? Do you have a core dump or back trace?
Comment by Grzegorz (gregosky) - Tuesday, 11 March 2014, 15:24 GMT
Apologies I bothered you Dave, reboot solved my issue.

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.

Loading...