[Bug 852643] New: ssh clients not disconnected when 13.1 host rebooted/shutdown
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c0 Summary: ssh clients not disconnected when 13.1 host rebooted/shutdown Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: novell@spam.somesuch.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 Any SSH clients connected to a remote openSUSE 13.1 host will not be disconnected by the host when the system is brought down. Instead the client is left to timeout. This differs from 12.3, which disconnects client connections. Reproducible: Always Steps to Reproduce: 1. ssh to a opensuse 13.1 host 2. type reboot 3. wait Actual Results: SSH client appears to remain connected to the remote host until finally it times out with a broken pipe error. Expected Results: SSH client to be disconnected by the remote host. This is tested on a clean DVD install on Vmware ESXi and Workstation. x86_64, minimal text install. I tried to get people in #opensuse to reproduce but nobody was interested in trying. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |os.gnome.maintainers@gmail. |ovo.novell.com |com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c1 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|os.gnome.maintainers@gmail. |bnc-team-screening@forge.pr |com |ovo.novell.com --- Comment #1 from Dominique Leuenberger <dimstar@opensuse.org> 2013-11-28 20:58:27 UTC --- Can;t see how this ended up on GNOME Team's queue... resetting assignee -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |pcerny@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c2 Petr Cerny <pcerny@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |novell@spam.somesuch.net --- Comment #2 from Petr Cerny <pcerny@suse.com> 2013-11-29 17:00:59 UTC --- Please check bug 822964 whether it sounds familiar. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c3 David Westfall <david.westfall@red-inc.us> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david.westfall@red-inc.us --- Comment #3 from David Westfall <david.westfall@red-inc.us> 2013-12-18 12:50:55 UTC --- I also have this problem. Two clean install from DVD and one upgrade from 12.2. Dave W -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c4 Richard Warner <rick@microway.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |rick@microway.com InfoProvider|novell@spam.somesuch.net | --- Comment #4 from Richard Warner <rick@microway.com> 2014-02-07 22:13:49 UTC --- I'm having the same problem. It seems to be caused by systemd stopping eth0 too early. I'm using openSuse 13.1 on a cluster. If I do "ssh node2 /sbin/reboot", it never comes back to a prompt. This worked fine on suse 12.3 and earlier versions. As a test, I modified /usr/lib/systemd/system/network@.service to have: ExecStop=echo dont stop now instead of ExecStop=/sbin/ifdown %i With it set like that, I was able to successfully "ssh node2 /sbin/reboot". I'm continuing to dig into the problem, but it seems like another case of systemd causing problems. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c5 --- Comment #5 from David Westfall <david.westfall@red-inc.us> 2014-02-13 18:15:28 UTC --- First, if systemd was more complicated it would be windows registry. Having said that I found the problem, The sshd.service does not have a Stop option in it like the init.d sshd file did. I added the following to sshd.service and did a reload of systemd. Now I get connection closed by remote host as soon as I reboot or do a power off. ExecStop=/usr/bin/killall sshd vi /usr/lib/systemd/system/sshd.service systemctl daemon-reload reboot Dave W -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c6 Flavio Castelli <fcastelli@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcastelli@suse.com --- Comment #6 from Flavio Castelli <fcastelli@suse.com> 2014-05-20 13:04:38 UTC --- I have the same problem. That's pretty annoying. Any chance to roll out an updated openssh package with the fix mentioned by comment #5? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c7 Thomas Wagner <wagner-thomas@gmx.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wagner-thomas@gmx.at --- Comment #7 from Thomas Wagner <wagner-thomas@gmx.at> 2014-07-16 09:01:07 UTC --- (In reply to comment #5)
ExecStop=/usr/bin/killall sshd Works for me too (at least for openSUSE 13.1 in KVM). However, I would really want to know why it works that way.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c8 --- Comment #8 from David Westfall <david.westfall@red-inc.us> 2014-07-16 16:53:41 UTC --- The difference between mine and Richard Warnner's fix is that I shutdown SSHD and he just stops the interface from shutting down. Programs that do not have a shutdown routine will be closed by the OS as it goes down. The problem with systemd is that it shutdowns the interface, then the OS shuts down SSHD. Because the interface is already down the remote client does not get the disconnect. There is most likely a better way then killall sshd, but the fix is to add an ExecStop to sshd.service in systemd. Dave W -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c9 --- Comment #9 from Thomas Wagner <wagner-thomas@gmx.at> 2014-07-17 09:47:42 UTC --- I just tried with the factory version and this bug seems to be there fixed already. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852643 https://bugzilla.novell.com/show_bug.cgi?id=852643#c10 Lars Behrens <lars.behrens@pi.uka.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lars.behrens@pi.uka.de --- Comment #10 from Lars Behrens <lars.behrens@pi.uka.de> 2014-08-15 10:03:54 UTC --- Can confirm this with a fresh install of 13.1, session at client side hangs when server goes away. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com