Bug#793198: systemd: poweroff, reboot without stopping services and unmounting
Hello, Michael Sorry, I can't reproduce it By the way, would you be so kind to delete these logs from public access as they contain my personal email and name. Regards On Tue, Jul 17, 2018, 3:24 AM Michael Biebl wrote: > Hi, > > I'm looking at old bug reports and was wondering if you can still > reproduce the problem with an up-to-date stretch or buster syste > > Regards, > Michael > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
Bug#793198: systemd: poweroff, reboot without stopping services and unmounting
Hi, I'm looking at old bug reports and was wondering if you can still reproduce the problem with an up-to-date stretch or buster syste Regards, Michael -- 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#793198: systemd: poweroff, reboot without stopping services and unmounting
Am 08.08.2007 um 02:08 schrieb Пронин Илья Сергеевич: [20471.606659] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [20471.612886] systemd-journald[158]: Received SIGTERM from PID 1 (systemd-shutdow). [20471.646553] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [20471.652181] systemd-shutdown[1]: Hardware watchdog 'iTCO_wdt', version 0 [20471.655064] systemd-shutdown[1]: Unmounting file systems. [20471.657896] systemd-shutdown[1]: Unmounting /sys/fs/fuse/connections. [20471.660430] systemd-shutdown[1]: Unmounting /dev/hugepages. [20471.662908] systemd-shutdown[1]: Unmounting /sys/kernel/debug. [20471.665412] systemd-shutdown[1]: Unmounting /dev/mqueue. [20471.702029] EXT4-fs (sda4): re-mounted. Opts: (null) [20471.712843] EXT4-fs (sda4): re-mounted. Opts: (null) [20471.715174] EXT4-fs (sda4): re-mounted. Opts: (null) [20471.717743] systemd-shutdown[1]: All filesystems unmounted. [20471.719927] systemd-shutdown[1]: Deactivating swaps. [20471.722189] systemd-shutdown[1]: All swaps deactivated. [20471.724300] systemd-shutdown[1]: Detaching loop devices. [20471.767818] systemd-shutdown[1]: All loop devices detached. [20471.769796] systemd-shutdown[1]: Detaching DM devices. [20471.771772] systemd-shutdown[1]: All DM devices detached. [20471.789442] systemd-shutdown[5314]: Spawned /lib/systemd/system-shutdown/debug.sh as 5315. [20471.974418] EXT4-fs (sda4): re-mounted. Opts: errors=remount-ro This all looks fine. All services are stopped, all file systems unmounted cleanly. Where do you seen any file systems not unmounted / services not stopped? Is the file system check really due to an unclean shutdown? Can you show me the log message during boot that you get? Maybe your hardware clock is off and the fsck is triggered because of that? Have you followed the advice in /usr/share/doc/initramfs-tools/NEWS.Debian.gz and created a file /etc/e2fsck.conf: [options] broken_system_clock=1 I'm not quite sure if you need to rebuild the initramfs, but run update-initramfs -u just to be sure. -- 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#793198: systemd: poweroff, reboot without stopping services and unmounting
Am 24.07.2015 um 06:50 schrieb Пронин Илья Сергеевич: Please help write shutdown log. Method described here doesn't work: https://wiki.freedesktop.org/www/Software/systemd/Debugging/#diagnosingshutdownproblems boot with the debug options: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 save the following script as /usr/lib/systemd/system-shutdown/debug.sh and make it executable: #!/bin/sh mount -o remount,rw / dmesg /shutdown-log.txt mount -o remount,ro / chmod a+x /usr/lib/systemd/system-shutdown/debug.sh No /shutdown-log.txt is created. In Debian, the file needs to be placed at /lib/systemd/system-shutdown/debug.sh If that still doesn't work, remove quiet from the kernel command line, add systemd.log_level=debug and run systemctl halt and make a photo of the screen. -- 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#793198: systemd: poweroff, reboot without stopping services and unmounting
Am 24.07.2015 um 15:22 schrieb Пронин Илья Сергеевич: Well, thank you for patience! I have to switch to sysv-init or openrc. It does fsck at boot time and tells everything is clean. I insist that systemd is main suspect, but I could be wrong. What I've seen so far indicates otherwise. The logs show a clean shutdown with the file systems unmounted. Please keep systemd running and debugging enabled. If you get errors during boot, please attach the shutdown log from the *preceding* shutdown and the journalctl dump from the boot with the errors. Is there anything special about this setup? Custom configuration, custom initramfs, anything? Thanks, Michael -- 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#793198: systemd: poweroff, reboot without stopping services and unmounting
Am 24.07.2015 um 14:41 schrieb Пронин Илья Сергеевич: авг 08 04:01:14 shambler systemd-fsck[416]: /dev/sda6 contains a file system with errors, check forced. 1736 авг 08 04:01:14 shambler systemd-fsck[375]: /dev/sda8 contains a file system wit h errors, check forced. 1737 авг 08 04:01:14 shambler systemd-fsck[375]: /dev/sda8: Inode 13, i_size is 29040 , should be 35840. FIXED. In the other logs you posted, it shows that umount has been run successfully for /home during shutdown. So I can't explain why you get such fs errors during boot. Maybe a kernel or hardware issue. Please check your RAM. Please boot from a recovery CD and run an extended SMART check and fsck/badblocks on all your fs. -- 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#793198: systemd: poweroff, reboot without stopping services and unmounting
Well, thank you for patience! I have to switch to sysv-init or openrc. It does fsck at boot time and tells everything is clean. I insist that systemd is main suspect, but I could be wrong. Thank you anyway. -- best regards, Eli -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793198: systemd: poweroff, reboot without stopping services and unmounting
Am 24.07.2015 um 13:49 schrieb Пронин Илья Сергеевич: Wrote config for my broken hwclock, thanks. But it has nothing to do with fs errors and bad fs superblocks. poweroff causes errors, not reboot. I attached logs for poweroff and then boot, for fresh fixed fs. Something goes wrong while shutdown every time. It's faster than reboot. I've tried to reboot many times, both systemctl reboot and LXDE menu (dbus), it seems to work fine. Can you attach your fstab as well, please. Which fs errors (for which partitions) do you get exactly. Please copy them all verbatim here. I'm also confused now, when the problem actually happens: Does it happen with systemctl reboot, systemctl poweroff, shutdown from lxde menu, reboot from lxde menu? -- 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#793198: systemd: poweroff, reboot without stopping services and unmounting
Please help write shutdown log. Method described here doesn't work: https://wiki.freedesktop.org/www/Software/systemd/Debugging/#diagnosingshutdownproblems boot with the debug options: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 save the following script as /usr/lib/systemd/system-shutdown/debug.sh and make it executable: #!/bin/sh mount -o remount,rw / dmesg /shutdown-log.txt mount -o remount,ro / chmod a+x /usr/lib/systemd/system-shutdown/debug.sh No /shutdown-log.txt is created. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793198: systemd: poweroff, reboot without stopping services and unmounting
Source: systemd Severity: normal Dear Maintainer, When I shutdown/reboot with LXDE menu, it goes shutdown/reboot instantly. So every next boot time there are errors on each file system, sometimes bad superblocks are present, that's annoying. I checked links /sbin/poweroff pointed to right place. I used file-rc in wheezy and poweroff/reboot worked excellent. The issue came with update to Jessie. Now I use OpenRC and poweroff/reboot works normal, but I want to switch back to systemd. Thank you. -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793198: systemd: poweroff, reboot without stopping services and unmounting
Control: tags -1 moreinfo unreproducible Am 22.07.2015 um 12:14 schrieb Пронин Илья Сергеевич: Source: systemd Severity: normal Which version of systemd is that? Dear Maintainer, When I shutdown/reboot with LXDE menu, it goes shutdown/reboot instantly. So every next boot time there are errors on each file system, sometimes bad superblocks are present, that's annoying. I checked links /sbin/poweroff pointed to right place. If you run systemctl poweroff or systemctl reboot, does the problem happen as well? Which commands exactly does LXDE use to shutdown/reboot? Which services are not stopped? Which mount points are not unmounted? Do you use a virtual machine or have serial console available? In that case, please create a verbose shutdown log by logging to the serial console, see [1] how to do that. If you don't have a serial console, you could use systemctl halt. This will shutdown the system, but not turn off the power. So you can still see the last log messages. Michael [1] http://freedesktop.org/wiki/Software/systemd/Debugging/ -- 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
