[Bug 790069] New: ssh session does not close on shutdown
https://bugzilla.novell.com/show_bug.cgi?id=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c0 Summary: ssh session does not close on shutdown Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rschweikert@suse.com QAContact: qa-bugs@suse.de CC: fcrozat@suse.com Found By: --- Blocker: --- With the latest update to systemd in Factory an ssh session no longer closes when a shutdown command is issued. Reproduce: - login via ssh to factory system with the latest systemd version - issue shutdown command Result: - The terminal is now "hung", i.e. the ssh client has no idea that the server went away Expected result: - The ssh client recognizes that the server is no longer there and exits The expected result was observed with previous versions of systemd, in the latest version this does no longer happen. -- 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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c Jiaying ren <jren@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jren@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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c1 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |rschweikert@suse.com --- Comment #1 from Frederic Crozat <fcrozat@suse.com> 2012-11-19 12:07:09 UTC --- I'm not able to reproduce this issue, ssh connection is correctly closed. Could you describe exactly if you login as simple user or root, if you have other sessions opened on VT and how you issued shutdown command (which session, under which identity) ? -- 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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c2 Robert Schweikert <rschweikert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|rschweikert@suse.com | --- Comment #2 from Robert Schweikert <rschweikert@suse.com> 2012-11-19 15:06:52 UTC --- I start an ssh session as a "regular" user, then "su -" to become root. Issuing "shutdown -h now" results in the "hung" ssh session. -- 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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c3 --- Comment #3 from Robert Schweikert <rschweikert@suse.com> 2012-11-19 15:11:03 UTC --- Created an attachment (id=513654) --> (http://bugzilla.novell.com/attachment.cgi?id=513654) logind startup failure -- 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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c4 --- Comment #4 from Robert Schweikert <rschweikert@suse.com> 2012-11-19 15:13:48 UTC --- After the shutdown command the systemd login deamon fails, see attachment. I suspect the issues are related. I can still ssh to the VM, but login is very slow. -- 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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c5 --- Comment #5 from Frederic Crozat <fcrozat@suse.com> 2012-11-19 15:23:59 UTC --- I don't have the issue, so indeed chances are very high it is logind related. -- 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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c6 --- Comment #6 from Frederic Crozat <fcrozat@suse.com> 2012-11-19 15:26:34 UTC --- could you give : systemctl status systemd-logind.service ? -- 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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c7 --- Comment #7 from Robert Schweikert <rschweikert@suse.com> 2012-11-19 15:37:30 UTC --- # systemctl status systemd-logind.service systemd-logind.service - Login Service Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static) Active: failed (Result: start-limit) since Mon, 2012-11-19 10:08:21 EST; 28min ago Docs: man:systemd-logind.service(8) man:logind.conf(5) http://www.freedesktop.org/wiki/Software/systemd/multiseat Main PID: 569 (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/systemd-logind.service Nov 19 10:08:21 googoo systemd[1]: Stopping Login Service... Nov 19 10:08:21 googoo systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE Nov 19 10:08:21 googoo systemd[1]: Failed to start Login Service. Nov 19 10:08:21 googoo systemd[1]: Unit systemd-logind.service entered failed state Nov 19 10:08:21 googoo systemd[1]: Stopping Login Service... Nov 19 10:08:21 googoo systemd[1]: Starting Login Service... Nov 19 10:08:21 googoo systemd[1]: Failed to start Login Service. Nov 19 10:08:21 googoo systemd[1]: Unit systemd-logind.service entered failed state -- 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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c8 --- Comment #8 from Robert Schweikert <rschweikert@suse.com> 2012-11-19 15:47:51 UTC --- # dmesg <snip> [ 4.421102] systemd[1]: systemd 195 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ; suse) [ 4.421172] systemd[1]: Detected virtualization 'kvm'. [ 4.445269] systemd[1]: Inserted module 'autofs4' [ 4.446759] systemd[1]: Set hostname to <googoo.rjsdomain>. [ 4.601383] systemd[1]: Cannot add dependency job for unit syslog.service, ignoring: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details. [ 4.601467] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details. [ 4.601845] systemd[1]: Started Collect Read-Ahead Data. [ 4.601869] systemd[1]: Started Replay Read-Ahead Data. [ 4.601885] systemd[1]: Starting Forward Password Requests to Wall Directory Watch. [ 4.601963] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 4.601978] systemd[1]: Starting Remote File Systems. [ 4.602190] systemd[1]: Reached target Remote File Systems. [ 4.602206] systemd[1]: Starting Delayed Shutdown Socket. [ 4.602362] systemd[1]: Listening on Delayed Shutdown Socket. [ 4.602375] systemd[1]: Starting /dev/initctl Compatibility Named Pipe. [ 4.602504] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [ 4.602540] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point. [ 4.602718] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 4.602729] systemd[1]: Starting Encrypted Volumes. [ 4.602831] systemd[1]: Reached target Encrypted Volumes. [ 4.602911] systemd[1]: Starting udev Kernel Socket. [ 4.603062] systemd[1]: Listening on udev Kernel Socket. [ 4.603128] systemd[1]: Starting udev Control Socket. [ 4.603250] systemd[1]: Listening on udev Control Socket. [ 4.603262] systemd[1]: Expecting device dev-disk-by\x2did-ata\x2dQEMU_HARDDISK_QM00001\x2dpart2.device... [ 4.603339] systemd[1]: Expecting device dev-disk-by\x2did-ata\x2dQEMU_HARDDISK_QM00001\x2dpart1.device... [ 4.603434] systemd[1]: Starting Journal Socket. [ 4.603570] systemd[1]: Listening on Journal Socket. [ 4.603584] systemd[1]: Starting LSB: Set default boot entry if called... [ 4.614290] systemd[1]: Starting udev Coldplug all Devices... [ 4.618664] systemd[1]: Mounting Huge Pages File System... [ 4.622358] systemd[1]: Mounting POSIX Message Queue File System... [ 4.652746] systemd[1]: Started Set Up Additional Binary Formats. [ 4.653764] systemd[1]: Starting Load Kernel Modules... [ 4.662443] systemd[1]: Starting Setup Virtual Console... [ 4.668513] systemd[1]: Started File System Check on Root Device. [ 4.668541] systemd[1]: Starting LSB: setup hostname and yp... [ 4.674231] systemd[1]: Starting Remount Root and Kernel File Systems... [ 4.680383] systemd[1]: Starting Journal Service... [ 4.689611] systemd[1]: Started Journal Service. [ 4.694462] systemd[1]: Starting udev Kernel Device Manager... [ 4.764673] systemd-udevd[282]: starting version 195 [ 4.787277] systemd-journald[280]: Failed to resolve 'adm' group: No such process [ 5.425943] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [ 5.427135] ACPI: Power Button [PWRF] [ 5.453290] parport_pc 00:05: reported by Plug and Play ACPI [ 5.453481] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [ 5.466568] FDC 0 is a S82078B [ 5.471563] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 5.471598] scsi 1:0:0:0: Attached scsi generic sg1 type 5 [ 5.484046] sr0: scsi3-mmc drive: 4x/4x xa/form2 tray [ 5.484050] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 5.484448] sr 1:0:0:0: Attached scsi CD-ROM sr0 [ 5.492642] piix4_smbus 0000:00:01.3: SMBus Host Controller at 0xb100, revision 0 [ 5.500469] input: PC Speaker as /devices/platform/pcspkr/input/input3 [ 5.511505] microcode: CPU0 sig=0x623, pf=0x0, revision=0x0 [ 5.512488] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [ 5.512679] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [ 5.529319] 8139cp 0000:00:03.0: eth0: RTL-8139C+ at 0xffffc900004b8000, 00:16:3e:7e:18:35, IRQ 11 [ 5.529367] 8139cp 0000:00:03.0: setting latency timer to 64 [ 5.557686] 8139too: 8139too Fast Ethernet driver 0.9.28 [ 5.579570] ppdev: user-space parallel port driver [ 5.608700] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba [ 5.860883] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 5.879427] EXT4-fs (sda1): mounted filesystem without journal. Opts: acl,user_xattr [ 5.958002] systemd-journald[280]: Received SIGUSR1 [ 6.070721] Adding 522236k swap on /dev/sda2. Priority:-1 extents:1 across:522236k [ 6.226496] systemd[1]: NetworkManager.service: control process exited, code=exited status=1 [ 6.230136] systemd[1]: Job NetworkManager-wait-online.service/start failed with result 'dependency'. [ 7.084743] systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start. [ 9.508284] 8139cp 0000:00:03.0: eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 -- 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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c9 --- Comment #9 from Robert Schweikert <rschweikert@suse.com> 2012-11-19 15:51:55 UTC --- Note that syslog-service is installed (see #790293) # rpm -qa | grep syslog syslog-service-1.4.1-762.1.noarch There does not appear to be a display-servive package, thus I am uncertain on how one would address the issue "Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load:" # zypper se display Loading repository data... Reading installed packages... S | Name | Summary | Type --+--------------------------+------------------------------------------+-------- | perl-Text-TabularDisplay | Display text in formatted table output | package | python-PyVirtualDisplay | Python wrapper for Xvfb, Xephyr and Xvnc | package | texlive-sasnrdisplay | Typeset SAS or R code or output | package | texlive-sasnrdisplay-doc | Documentation for texlive-sasnrdisplay | package -- 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=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c10 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #10 from Frederic Crozat <fcrozat@suse.com> 2013-06-14 02:17:29 UTC --- This has been fixed in Factory before 12.3. closing -- 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