Bug#763028: systemd-sysv shutdown and reboot hang system
Hi, just want to state that I am struck by this bug for a while now. Just started today searching for a solution. On Wed, 1 Apr 2015 11:10:21 +0200 Martin Pittwrote: > Yesterday we found quite a fundamental flaw related to how D-Bus is > stopped during shutdown [1]. It might be worth a try to edit > /lib/systemd/system/dbus.service and append these two lines to the > [Service] section: > > ExecStop=/bin/true > KillMode=none > > Then run "systemctl daemon-reload" as root. Does this improve shutdown > for any of you? No change in behavior at all. > Note that this is certainly not a magic bullet for all kinds of > shutdown problems, especially since the reports/data here is vague > enough that these might very well be different reasons. But it would > be interesting to see if it makes a difference for any of you. The > Ubuntu bug https://launchpad.net/bugs/1427672 was linked to this > Debian one and found to be fixed with the above D-Bus change. Hmm, from my reading they say (in the end) "Don't do that !". But however, it didn't solve anything here, so I removed the two lines. I waited for a timeout a complete night, nothing happened. I have to tip the reset (hardware) button or press the poweroff knob for 5s. What works is ALT + PrintScreen + REISUB. But still my filesystems (several VMs running) are broken from time to time (e.g. one of the ReiserFS VMs needs a fsck.reiserfs --rebuild-tree, else it denies booting). I have Samba installed (but can't uninstall it for testing), no squid installed. I am on Debian SID amd64 (up-to-date packages). What exactly can I do to help fixing this bug ? signature.asc Description: This is a digitally signed message part.
Bug#763028: systemd-sysv shutdown and reboot hang system
Hello all, Yesterday we found quite a fundamental flaw related to how D-Bus is stopped during shutdown [1]. It might be worth a try to edit /lib/systemd/system/dbus.service and append these two lines to the [Service] section: ExecStop=/bin/true KillMode=none Then run systemctl daemon-reload as root. Does this improve shutdown for any of you? Note that this is certainly not a magic bullet for all kinds of shutdown problems, especially since the reports/data here is vague enough that these might very well be different reasons. But it would be interesting to see if it makes a difference for any of you. The Ubuntu bug https://launchpad.net/bugs/1427672 was linked to this Debian one and found to be fixed with the above D-Bus change. Thanks, Martin [1] https://bugs.freedesktop.org/show_bug.cgi?id=89847 -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763028: systemd-sysv shutdown and reboot hang system
Hallo, * Michael Biebl [Sat, Sep 27 2014, 11:59:05AM]: Control: tags -1 moreinfo Am 27.09.2014 um 11:47 schrieb Aquila Rubra: Package: systemd-sysv Version: 215-4 When I launch shutdown -h now or reboot, I get a black screen immediately and the system hangs so indefinitely. How long did you wait? I have to manually power off the computer. This happened after the last dist-upgrade in sid. Does this happen on every reboot, i.e. is the problem reproducible? I think this also happens to me now and is reproducible. ii systemd215-5+b1 amd64system and service manager Here is a screenshot: https://www.unix-ag.uni-kl.de/~bloch/.debian/IMG_20140923_215621.jpg If I press Ctrl-Alt-Del while it is in hanging state, it attempts to restart a couple of tasks, see picture. If I do that twice withing a second, it prints FAILED messages. Looks totally crazy. Regards, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763028: Fwd: Bug#763028: systemd-sysv shutdown and reboot hang system
I have now version 215-5 and the issue is same. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763028: Fwd: Bug#763028: systemd-sysv shutdown and reboot hang system
I booted already with systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 On shutdown, nothing is printed. At once, as the command is given, everything disappears and the screen turns to black. There is no apparent activity. It just stays like that. On Sat, Sep 27, 2014 at 5:53 PM, Michael Biebl bi...@debian.org wrote: Am 27.09.2014 um 16:52 schrieb Aquila Rubra: Am 27.09.2014 um 11:47 schrieb Aquila Rubra: Package: systemd-sysv Version: 215-4 When I launch shutdown -h now or reboot, I get a black screen immediately and the system hangs so indefinitely. How long did you wait? Up to 20 minutes. I have to manually power off the computer. This happened after the last dist-upgrade in sid. Does this happen on every reboot, i.e. is the problem reproducible? Yes, it happens always. I cannot turn off the computer any longer. I reinstalled Wheezy, upgraded again to Sid, and it happened again. It did not happen one month ago with the previous dist-upgrade. I use amd64 with lxde. Can you follow the instructions from [1] and get us a debug log from the shutdown sync reboot -f works (The debug.sh script needs to be saved under /lib/systemd/system-shutdown/ in Debian, not /usr) /shutdown-log.txt is not even created. If you enable verbose mode, what is the last message you get? [1] http://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 This is the last thing I get from syslog. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-1. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-1. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-1. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-1. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-1. Sep 27 16:35:45 phantom systemd[1]: Stopping Session 1 of user phantom. Sep 27 16:35:45 phantom systemd[1]: Stopped Session 1 of user phantom. Sep 27 16:35:45 phantom systemd[1]: Stopping Session c1 of user lightdm. Sep 27 16:35:45 phantom systemd[1]: Stopped Session c1 of user lightdm. Sep 27 16:35:45 phantom kernel: [ 171.752051] wlan0: deauthenticating from 00:a0:a2:45:3a:5d by local choice (Reason: 3=DEAU$ Sep 27 16:35:45 phantom systemd[1]: Stopping Sound Card. Sep 27 16:35:45 phantom systemd[1]: Stopped target Sound Card. Sep 27 16:35:45 phantom systemd[1]: Stopping system-systemd\x2dfsck.slice. Sep 27 16:35:45 phantom systemd[1]: Removed slice system-systemd\x2dfsck.slice. Sep 27 16:35:45 phantom systemd[1]: Stopping Console Manager... Sep 27 16:35:45 phantom systemd[1]: Stopping Disk Manager... Sep 27 16:35:45 phantom systemd[1]: Stopping User Manager for UID 1000... Sep 27 16:35:45 phantom systemd[1]: Stopping User Manager for UID 105... Sep 27 16:35:45 phantom systemd[1]: Stopping WPA supplicant... Sep 27 16:35:45 phantom systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks... Sep 27 16:35:45 phantom systemd[1]: Stopping Graphical Interface. Sep 27 16:35:45 phantom systemd[1]: Stopped target Graphical Interface. Sep 27 16:35:45 phantom systemd[1]: Stopping Light Display Manager... Sep 27 16:35:45 phantom systemd[1]: Stopping Multi-User System. Sep 27 16:35:45 phantom systemd[1]: Stopped target Multi-User System. Sep 27 16:35:45 phantom systemd[1]: Stopping Regular background program processing daemon... Sep 27 16:35:45 phantom systemd[1]: Stopping Network Manager... Sep 27 16:35:45 phantom rsyslogd: [origin software=rsyslogd swVersion=8.4.0 x-pid=844 x-info=http://www.rsyslog.com;] exiting on signal 15. If you can access the debug shell on tty9, what processes are running (ps aux) and what's the output of systemctl list-jobs. No console is accessible. The disks do not spin. It just stays like that without powering off. Can you boot with systemd.log_level=debug and create a screenshot with a camera to see the last message that is printed by systemd on shutdown. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763028: Fwd: Bug#763028: systemd-sysv shutdown and reboot hang system
Am 01.10.2014 um 12:20 schrieb Aquila Rubra: I booted already with systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 On shutdown, nothing is printed. At once, as the command is given, everything disappears and the screen turns to black. There is no apparent activity. It just stays like that. Can you drop the systemd.log_target=kmsg and try again. Can you also attach the output of all your installed packages, a systemd-analyze dump and journalctl -alb dump thanks. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#763028: systemd-sysv shutdown and reboot hang system
hi I have the same problem and I solved it by uninstalling samba # Apt-get remove samba I still have the black screen but the computer shuts down. ps: excuse me for my bad english -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763028: systemd-sysv shutdown and reboot hang system
Package: systemd-sysv Version: 215-4 When I launch shutdown -h now or reboot, I get a black screen immediately and the system hangs so indefinitely. I have to manually power off the computer. This happened after the last dist-upgrade in sid. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763028: systemd-sysv shutdown and reboot hang system
Control: tags -1 moreinfo Am 27.09.2014 um 11:47 schrieb Aquila Rubra: Package: systemd-sysv Version: 215-4 When I launch shutdown -h now or reboot, I get a black screen immediately and the system hangs so indefinitely. How long did you wait? I have to manually power off the computer. This happened after the last dist-upgrade in sid. Does this happen on every reboot, i.e. is the problem reproducible? Can you follow the instructions from [1] and get us a debug log from the shutdown (The debug.sh script needs to be saved under /lib/systemd/system-shutdown/ in Debian, not /usr) If you enable verbose mode, what is the last message you get? If you can access the debug shell on tty9, what processes are running (ps aux) and what's the output of systemctl list-jobs. Thanks. [1] http://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#763028: systemd-sysv shutdown and reboot hang system
Am 27.09.2014 um 16:52 schrieb Aquila Rubra: Am 27.09.2014 um 11:47 schrieb Aquila Rubra: Package: systemd-sysv Version: 215-4 When I launch shutdown -h now or reboot, I get a black screen immediately and the system hangs so indefinitely. How long did you wait? Up to 20 minutes. I have to manually power off the computer. This happened after the last dist-upgrade in sid. Does this happen on every reboot, i.e. is the problem reproducible? Yes, it happens always. I cannot turn off the computer any longer. I reinstalled Wheezy, upgraded again to Sid, and it happened again. It did not happen one month ago with the previous dist-upgrade. I use amd64 with lxde. Can you follow the instructions from [1] and get us a debug log from the shutdown sync reboot -f works (The debug.sh script needs to be saved under /lib/systemd/system-shutdown/ in Debian, not /usr) /shutdown-log.txt is not even created. If you enable verbose mode, what is the last message you get? [1] http://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 This is the last thing I get from syslog. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-0. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-1. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-1. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-1. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-1. Sep 27 16:35:45 phantom systemd[1]: Stopping /sys/devices/virtual/block/dm-1. Sep 27 16:35:45 phantom systemd[1]: Stopping Session 1 of user phantom. Sep 27 16:35:45 phantom systemd[1]: Stopped Session 1 of user phantom. Sep 27 16:35:45 phantom systemd[1]: Stopping Session c1 of user lightdm. Sep 27 16:35:45 phantom systemd[1]: Stopped Session c1 of user lightdm. Sep 27 16:35:45 phantom kernel: [ 171.752051] wlan0: deauthenticating from 00:a0:a2:45:3a:5d by local choice (Reason: 3=DEAU$ Sep 27 16:35:45 phantom systemd[1]: Stopping Sound Card. Sep 27 16:35:45 phantom systemd[1]: Stopped target Sound Card. Sep 27 16:35:45 phantom systemd[1]: Stopping system-systemd\x2dfsck.slice. Sep 27 16:35:45 phantom systemd[1]: Removed slice system-systemd\x2dfsck.slice. Sep 27 16:35:45 phantom systemd[1]: Stopping Console Manager... Sep 27 16:35:45 phantom systemd[1]: Stopping Disk Manager... Sep 27 16:35:45 phantom systemd[1]: Stopping User Manager for UID 1000... Sep 27 16:35:45 phantom systemd[1]: Stopping User Manager for UID 105... Sep 27 16:35:45 phantom systemd[1]: Stopping WPA supplicant... Sep 27 16:35:45 phantom systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks... Sep 27 16:35:45 phantom systemd[1]: Stopping Graphical Interface. Sep 27 16:35:45 phantom systemd[1]: Stopped target Graphical Interface. Sep 27 16:35:45 phantom systemd[1]: Stopping Light Display Manager... Sep 27 16:35:45 phantom systemd[1]: Stopping Multi-User System. Sep 27 16:35:45 phantom systemd[1]: Stopped target Multi-User System. Sep 27 16:35:45 phantom systemd[1]: Stopping Regular background program processing daemon... Sep 27 16:35:45 phantom systemd[1]: Stopping Network Manager... Sep 27 16:35:45 phantom rsyslogd: [origin software=rsyslogd swVersion=8.4.0 x-pid=844 x-info=http://www.rsyslog.com;] exiting on signal 15. If you can access the debug shell on tty9, what processes are running (ps aux) and what's the output of systemctl list-jobs. No console is accessible. The disks do not spin. It just stays like that without powering off. Can you boot with systemd.log_level=debug and create a screenshot with a camera to see the last message that is printed by systemd on shutdown. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature