[Bug 822964] New: with systemd ssh connections hang when doing a re-boot
https://bugzilla.novell.com/show_bug.cgi?id=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c0 Summary: with systemd ssh connections hang when doing a re-boot Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: support@microtechniques.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20130518 Firefox/20.0 PaleMoon/20.1 Since upgrading to 12.3 with systemd about half my systems hang the ssh connection when I remotely re-boot the system. In earlier versions, there were several seconds after doing a shutdown -? now when you could do an 'exit' before the network went down. In 12.2, the system closed the connection for you, and you did not have to issue an 'exit'. In 12.3, the system does not always close the connection, and there is not enough time to issue the 'exit' yourself, leaving the terminal session hung. However, this does not happen for all of my systems, a few still behave in the 12.2 fashion. I am assuming that this is an systemd artifact, and not a change to the ssh daemon since all of the systems are running the same version of ssh. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c Ye Yuan <yyuan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |fcrozat@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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c1 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |pcerny@suse.com --- Comment #1 from Frederic Crozat <fcrozat@suse.com> 2013-06-04 02:19:24 UTC --- I don't think it is caused by systemd but maybe by the changes which went into openssh .service (compared to its initscript). -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c2 --- Comment #2 from Don Hughes <support@microtechniques.com> 2013-06-04 11:32:46 UTC --- Created an attachment (id=542568) --> (http://bugzilla.novell.com/attachment.cgi?id=542568) System log from failing system -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c3 --- Comment #3 from Don Hughes <support@microtechniques.com> 2013-06-04 11:33:19 UTC --- Created an attachment (id=542569) --> (http://bugzilla.novell.com/attachment.cgi?id=542569) System log from working system -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c4 --- Comment #4 from Don Hughes <support@microtechniques.com> 2013-06-04 11:44:51 UTC --- The /usr/lib/systemd/system/sshd.service, /etc/sysconfig/ssh, and /etc/ssh/sshd_conf files are the same on all the systems. I have attached log files from two of the systems - one where the connection hangs, and one where it is closed. You can see that the order of stopping sshd, tty, and the network have been reversed. -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c5 Petr Cerny <pcerny@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|Basesystem |Basesystem InfoProvider| |fcrozat@suse.com AssignedTo|pcerny@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 12.2 |openSUSE 12.3 --- Comment #5 from Petr Cerny <pcerny@suse.com> 2013-06-04 13:04:04 UTC --- Hmm, the log file also says "Stopped OpenSSH" on the working machine while "Stopping OpenSSH" on the problematic one is reported. Frederic, could the problem be possibly fixed by adding something like ExecStop=killproc -p $SSHD_PIDFILE -TERM $SSHD_BIN which is used in SysV init script? -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c6 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |fcrozat@suse.com InfoProvider|fcrozat@suse.com | --- Comment #6 from Frederic Crozat <fcrozat@suse.com> 2013-06-05 02:26:04 UTC --- using ExecStop=/bin/kill -TERM $MAINPID should do the same (since systemd is tracking the PID, there is no need to use killproc and I don't think a PID file is being created when using systemd) although I'm not sure it will make a big difference compared to what systemd is doing by default (see man systemd.kill, section killmode) -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c Ye Yuan <yyuan@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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c7 Petr Cerny <pcerny@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |support@microtechniques.com --- Comment #7 from Petr Cerny <pcerny@suse.com> 2013-07-19 16:07:48 UTC --- Don, can you please try Frederic's suggestion - i.e. adding ExecStop=/bin/kill -TERM $MAINPID to the [Service] section in the sshd's .service file? -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c8 --- Comment #8 from Don Hughes <support@microtechniques.com> 2013-08-09 13:14:57 UTC --- I re-tested prior to making Frederic's suggested changes, and found that all of the connections are now closing as expected. Evidently this was fixed by some other Tumbleweed update. You can close this issue. -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c Don Hughes <support@microtechniques.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|support@microtechniques.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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c9 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |FIXED --- Comment #9 from Frederic Crozat <fcrozat@suse.com> 2013-08-30 15:19:00 UTC --- closing as fixed -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c10 Richard Weinberger <richard@nod.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED CC| |richard@nod.at Resolution|FIXED | --- Comment #10 from Richard Weinberger <richard@nod.at> 2014-02-04 14:48:08 UTC --- The problem seems to be present in 13.1 (again?). sauron:~ # reboot Timeout, server 10.1.1.242 not responding. It looks like a race between ifdown and killing sshd. log: Feb 04 14:41:42 sauron systemd[2042]: Startup finished in 111ms. Feb 04 14:41:42 sauron systemd[1]: Started User Manager for 0. Feb 04 14:42:40 sauron systemd[1]: Stopping Session 1 of user root. Feb 04 14:42:40 sauron systemd[1]: Stopped Session 1 of user root. Feb 04 14:42:40 sauron systemd[1]: Stopping Virtual Machine qemu-builder_troll. Feb 04 14:42:40 sauron systemd[1]: Stopping System Time Synchronized. Feb 04 14:42:40 sauron systemd[1]: Stopped target System Time Synchronized. Feb 04 14:42:40 sauron systemd[1]: Stopping Stop Read-Ahead Data Collection 10s After Completed Startup. Feb 04 14:42:40 sauron systemd[1]: Stopped Stop Read-Ahead Data Collection 10s After Completed Startup. Feb 04 14:42:40 sauron systemd[1]: Stopping User Manager for 0... Feb 04 14:42:40 sauron systemd[1]: Stopping ifup managed network interface br0... Feb 04 14:42:40 sauron systemd[1]: Stopping ifup managed network interface enp16s0... Feb 04 14:42:40 sauron systemd[1]: Stopping Multi-User System. Feb 04 14:42:40 sauron systemd[1]: Stopped target Multi-User System. Feb 04 14:42:40 sauron systemd[1]: Stopping LSB: Network time protocol daemon (ntpd)... Feb 04 14:42:40 sauron systemd[1]: Stopping Command Scheduler... Feb 04 14:42:40 sauron systemd[1]: Stopping Suspend Active Libvirt Guests... Feb 04 14:42:40 sauron systemd[1]: Stopping OpenSSH Daemon... Feb 04 14:42:40 sauron systemd[1]: Stopping System statistics collection daemon... Feb 04 14:42:40 sauron systemd[2042]: Stopping Default. Feb 04 14:42:40 sauron libvirtd[1789]: internal error: End of file from monitor Feb 04 14:42:40 sauron systemd[1]: Stopping /etc/init.d/after.local Compatibility... Feb 04 14:42:40 sauron systemd[2042]: Stopped target Default. Feb 04 14:42:40 sauron systemd[1]: Stopped /etc/init.d/after.local Compatibility. Feb 04 14:42:40 sauron systemd[2042]: Starting Shutdown. Feb 04 14:42:40 sauron systemd[1]: Stopping Login Prompts. Feb 04 14:42:40 sauron systemd[2042]: Reached target Shutdown. Feb 04 14:42:40 sauron systemd[1]: Stopped target Login Prompts. Feb 04 14:42:40 sauron systemd[2042]: Starting Exit the Session... Feb 04 14:42:40 sauron systemd[1]: Stopping Getty on tty1... Feb 04 14:42:40 sauron systemd[1]: Stopping Virtual Machine and Container Registration Service... Feb 04 14:42:40 sauron sshd[1816]: Received signal 15; terminating. Feb 04 14:42:40 sauron collectd[1788]: Exiting normally. Feb 04 14:42:40 sauron collectd[1788]: collectd: Stopping 5 read threads. Feb 04 14:42:40 sauron kernel: br0: port 2(vnet0) entered disabled state Feb 04 14:42:40 sauron systemd[1]: Stopping Login Service... Feb 04 14:42:40 sauron kernel: device vnet0 left promiscuous mode Feb 04 14:42:40 sauron kernel: br0: port 2(vnet0) entered disabled state Feb 04 14:42:40 sauron systemd[1]: Stopped Command Scheduler. Feb 04 14:42:40 sauron systemd[1]: Stopped OpenSSH Daemon. Feb 04 14:42:40 sauron systemd[1]: Stopped Getty on tty1. Feb 04 14:42:40 sauron systemd[1]: Stopped Virtual Machine and Container Registration Service. Feb 04 14:42:40 sauron systemd[1]: Stopping The Apache Webserver... Feb 04 14:42:40 sauron systemd[1]: Stopping system-getty.slice. Feb 04 14:42:40 sauron systemd[1]: Removed slice system-getty.slice. Feb 04 14:42:40 sauron systemd[1]: Stopping /etc/init.d/boot.local Compatibility... -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c11 --- Comment #11 from Don Hughes <support@microtechniques.com> 2014-02-04 15:46:31 UTC --- I was also just about to re-open this issue. I am now seeing the same results as reported by Richard on all of my 13.1 systems. -- 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=822964 https://bugzilla.novell.com/show_bug.cgi?id=822964#c12 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #12 from Frederic Crozat <fcrozat@suse.com> 2014-02-04 16:01:41 UTC --- please open a separate bug report for 13.1, this bug is about 12.3 and I'm pretty sure you are seeing another different bug. Closing back. -- 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