Quantcast
Channel: SuSE Linux – The Wiert Corner – irregular stream of stuff
Viewing all articles
Browse latest Browse all 217

reboot fixes “pam_systemd(sshd:session): Failed to create session: Connection timed out” need to find the cause.

$
0
0

In case I get something similar to this again:

Mar 11 12:54:06 filesrepo sshd[22021]: Accepted publickey for SOMEUSER from xxx.xxx.xxx.xxx port xxxxx ssh2: RSA xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
Mar 11 12:54:06 filesrepo kernel: type=1006 audit(1394542446.943:117): pid=22021 uid=0 old auid=4294967295 new auid=1019 old ses=4294967295 new ses=116 res=1
Mar 11 12:54:06 filesrepo sshd[22021]: pam_unix(sshd:session): session opened for user SOMEUSER by (uid=0)
Mar 11 12:54:06 filesrepo dbus[421]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Mar 11 12:54:31 filesrepo sshd[22021]: pam_systemd(sshd:session): Failed to create session: Connection timed out
Mar 11 12:54:31 filesrepo dbus[421]: [system] Failed to activate service 'org.freedesktop.login1': timed out
Mar 11 12:54:31 filesrepo dbus[421]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Mar 11 12:54:32 filesrepo svnserve[22061]: DIGEST-MD5 common mech free
Mar 11 12:54:32 filesrepo sshd[22021]: pam_unix(sshd:session): session closed for user SOMEUSER

I have been noticing this for last few days but I thought systemd update should solve this (bug report was raised against systemd)

I updated system today (I have not given it a reboot yet) and I still see those logs.

Rebooting fixed this issue.

But I’m not sure about the cause.

–jeroen

via: [closed] pam_unix(sshd:session) timeouts / Networking, Server, and Protection / Arch Linux Forums.


Filed under: *nix, Linux, openSuSE, Power User, SuSE Linux

Viewing all articles
Browse latest Browse all 217

Trending Articles