http://bugzilla.opensuse.org/show_bug.cgi?id=929564
http://bugzilla.opensuse.org/show_bug.cgi?id=929564#c6
--- Comment #6 from andreas bittner ---
I am logging into a sshd that is experiencing these problems right now.
Is it possible that it is (again) related to some dbus stuff (I used to have
bugreports on dbus (restarting it) making x server or displaymanager or
something go ballistic and eat all cpu and such stuff)
this is currently in my logs on the machine (42.1)
ssh client (putty) log:
(current delay: access granted delta to started shell command)
2016-05-31 17:17:39 Initialised AES-256 SDCTR client->server encryption
2016-05-31 17:17:39 Initialised HMAC-SHA-256 client->server MAC algorithm
2016-05-31 17:17:39 Initialised AES-256 SDCTR server->client encryption
2016-05-31 17:17:39 Initialised HMAC-SHA-256 server->client MAC algorithm
2016-05-31 17:17:42 Attempting keyboard-interactive authentication
2016-05-31 17:17:45 Access granted
2016-05-31 17:17:45 Initiating key re-exchange (enabling delayed
compression)
2016-05-31 17:17:45 Opening session as main channel
2016-05-31 17:18:10 Server supports delayed compression; will try this later
2016-05-31 17:18:10 Doing ECDH key exchange with curve Curve25519 and hash
SHA-256
2016-05-31 17:18:11 Initialised AES-256 SDCTR client->server encryption
2016-05-31 17:18:11 Initialised HMAC-SHA-256 client->server MAC algorithm
2016-05-31 17:18:11 Initialised zlib (RFC1950) compression
2016-05-31 17:18:11 Initialised AES-256 SDCTR server->client encryption
2016-05-31 17:18:11 Initialised HMAC-SHA-256 server->client MAC algorithm
2016-05-31 17:18:11 Initialised zlib (RFC1950) decompression
2016-05-31 17:18:11 Opened main channel
2016-05-31 17:18:11 Allocated pty (ospeed 38400bps, ispeed 38400bps)
2016-05-31 17:18:11 Started a shell/command
journalctl:
May 31 17:17:33 tux01 sshd[4463]: Accepted keyboard-interactive/pam for
testuser from myip port 4369 ssh2
May 31 17:17:33 tux01 sshd[4463]: pam_unix(sshd:session): session opened for
user testuser by (uid=0)
May 31 17:17:33 tux01 dbus[5910]: [system] Activating via systemd: service
name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
May 31 17:17:33 tux01 systemd[1]: Cannot add dependency job for unit
logrotate.timer, ignoring: Unit logrotate.timer failed to load: No such file or
directory.
May 31 17:17:58 tux01 sshd[4463]: pam_systemd(sshd:session): Failed to create
session: Connection timed out
May 31 17:17:58 tux01 dbus[5910]: [system] Failed to activate service
'org.freedesktop.login1': timed out
May 31 17:18:05 tux01 su[4501]: (to root) testuser on pts/0
May 31 17:18:05 tux01 su[4501]: pam_unix(su-l:session): session opened for user
root by testuser(uid=1000)
May 31 17:18:05 tux01 dbus[5910]: [system] Activating via systemd: service
name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
May 31 17:18:05 tux01 systemd[1]: Cannot add dependency job for unit
logrotate.timer, ignoring: Unit logrotate.timer failed to load: No such file or
directory.
May 31 17:18:30 tux01 su[4501]: pam_systemd(su-l:session): Failed to create
session: Connection timed out
May 31 17:18:30 tux01 dbus[5910]: [system] Failed to activate service
'org.freedesktop.login1': timed out
the su- command took about the same amount of time to succeed.
Also this machine has been updated (zypper up) some days ago and I think there
were some systemd and other updates. I really think that there is some services
depending on each other or not properly (re)started after the zypper up (and I
sysctl restart ...... various services that I see via zypper ps).
Anyone able to help? Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.