[Bug 2573] New: dead sessions cannot be closed with ~.
bugzilla-daemon at bugzilla.mindrot.org
bugzilla-daemon at bugzilla.mindrot.org
Thu May 26 13:27:02 AEST 2016
https://bugzilla.mindrot.org/show_bug.cgi?id=2573
Bug ID: 2573
Summary: dead sessions cannot be closed with ~.
Product: Portable OpenSSH
Version: 3.7.1p2
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: ssh
Assignee: unassigned-bugs at mindrot.org
Reporter: calestyo at scientia.net
Hey.
This is may be the client-side counterpart to bug #2572.
Versions, distro, etc., all as there, i.e. I also think it may have
started with 6.9 (but I may be wrong her).
Every now and then, when some connections get stuck (it e.g. happens
sometimes, but not always, when I reboot the server, and Debian's ssh
systemd units do not yet properly close ssh connections before they
kill networking, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636), ~. doesn't
work anymore to terminate the session/client.
Similarly, but perhaps another issue comes happens during this
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770135 ... see also
its duplicate reports there):
When dbus is restarted, something gets apparently wrong with
systemd-logind... and the logins with ssh are considerably delayed
(until they finally succeed when something in systemd or so times out).
Now this is a systemd/dbus/whatever problem,... BUT... during the
server hangs, because of that bug,... the client side hangs either.
Neither ~. nor Ctrl-C work then (even though no remote shell login has
happened yet)
Amongst other, my ssh_config has:
TCPKeepAlive no
ServerAliveInterval 15
ServerAliveCountMax 8
But right now, I cannot really tell if the client also seems to fail
enforcing the Alive, as the server does (Bug 2572)... will wait for the
8*15s period next time it happens.
Any ideas?
Chris.
--
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the openssh-bugs
mailing list