Hi
for me some times to take a long time to shut down or reboot.
is it normal?
How do I find. the problem?
how to see log reboot?
Thanks
Well booting is shown with systemd-analyze blame or critical-chain
You can examine log from previous boot using
sudo journalctl -b 1
I don’t know the answer. But, for me, it seems to take longer than it should.
The very worst for me was with 13.2 on my laptop. There, it seemed to shutdown NetworkManager before it unmounted NFS mounts. And that caused an infinite hang (I had to power off). I think they have since fixed that. My workaround, at the time, was to switch to using “wicked” to configure the network. I have lot seen that problem on 42.1.
Apart from that problem, it seems to me that 13.2 took longer than 13.1 to shutdown. And 42.1 takes even longer.
I have not tried to investigate the reasons.
hi,
the journals can slow the boot if allowed to increase in size,
what are the file sizes of the files in,
/var/log/journal/<32 bit word>/ with today’s date?
user-<XXX>.journal and system-<XXX>.journal
changes in /etc/systemd/journald.conf can limit the space used
if using a non-national NTP server for time sync,
can also slow boot and shut down times.
This can be checked in -yast --NTP Configuration —General Settings
observation
using -Leave --Hiberate (Suspend to disk), can be quicker than boot and Shutdown
ymmv
Thank you all for help
log for me
systemd-analyze blame
~> systemd-analyze blame
15.131s display-manager.service
12.476s ModemManager.service
11.232s avahi-daemon.service
11.163s SuSEfirewall2_init.service
10.928s bluetooth.service
6.369s systemd-cryptsetup@cr_ata\x2dST1000LM024_HN\x2dM101MBB_S31LJ9EDC04182\x2dpart13.service
5.377s lvm2-pvscan@254:0.service
3.086s dev-mapper-system\x2droot.device
2.637s SuSEfirewall2.service
2.632s systemd-fsck@dev-disk-by\x2duuid-e285fbbd\x2d72f9\x2d4783\x2da7b7\x2d53f9e7d03b14.service
1.561s run-media-think_alone-show_other.mount
1.394s run-media-think_alone-serial2.mount
1.330s systemd-journald.service
1.322s systemd-tmpfiles-setup-dev.service
1.317s vboxdrv.service
1.315s postfix.service
1.241s polkit.service
1.067s systemd-fsck-root.service
1.009s sys-kernel-debug.mount
1.009s dev-mqueue.mount
1.007s dev-hugepages.mount
911ms rtkit-daemon.service
695ms systemd-tmpfiles-setup.service
688ms user@1000.service
552ms systemd-fsck@dev-system-home.service
544ms systemd-udev-trigger.service
454ms systemd-readahead-replay.service
367ms plymouth-read-write.service
313ms home.mount
270ms apparmor.service
199ms systemd-backlight@backlight:intel_backlight.service
159ms systemd-modules-load.service
156ms systemd-sysctl.service
136ms console-kit-log-system-start.service
124ms boot-efi.mount
100ms kmod-static-nodes.service
97ms NetworkManager.service
89ms systemd-udevd.service
81ms systemd-readahead-collect.service
73ms console-kit-daemon.service
68ms wpa_supplicant.service
68ms ofono.service
66ms systemd-user-sessions.service
65ms nscd.service
63ms rc-local.service
63ms alsa-restore.service
60ms systemd-remount-fs.service
59ms systemd-udev-root-symlink.service
46ms udisks2.service
27ms plymouth-start.service
17ms dev-system-swap.swap
11ms boot.mount
10ms systemd-vconsole-setup.service
5ms upower.service
4ms systemd-logind.service
4ms auditd.service
3ms systemd-update-utmp.service
2ms systemd-journal-flush.service
2ms iscsi.service
2ms systemd-update-utmp-runlevel.service
1ms systemd-readahead-done.service
1ms systemd-rfkill@rfkill1.service
1ms systemd-random-seed.service
1ms sys-fs-fuse-connections.mount
1ms systemd-rfkill@rfkill0.service
sudo journalctl -b 1
May 11 12:29:40 linux-e1rt NetworkManager[1592]: **<warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.prot**
May 11 12:29:40 linux-e1rt NetworkManager[1592]: **<warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open**
May 11 12:29:40 linux-e1rt NetworkManager[1592]: <info> caught SIGTERM, shutting down normally.
May 11 12:29:40 linux-e1rt NetworkManager[1592]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'unmanaged
May 11 12:29:41 linux-e1rt NetworkManager[1592]: <info> (wlan0): device state change: disconnected -> unmanaged (reason 'unmanag
May 11 12:29:41 linux-e1rt bluetoothd[1473]: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSink
May 11 12:29:41 linux-e1rt bluetoothd[1473]: Disconnected from D-Bus. Exiting.
May 11 12:29:41 linux-e1rt bluetoothd[1473]: Stopping SDP server
May 11 12:29:41 linux-e1rt bluetoothd[1473]: Exit
May 11 12:29:41 linux-e1rt kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 11 12:29:40 linux-e1rt sddm[1817]: **Authentication error: "Process crashed"**
May 11 12:29:40 linux-e1rt sddm[1817]: **Auth: sddm-helper crashed (exit code 15)**
May 11 12:29:40 linux-e1rt sddm[1817]: **Authentication error: "Process crashed"**
May 11 12:29:40 linux-e1rt sddm[1817]: **Auth: sddm-helper exited with 15**
May 11 12:29:40 linux-e1rt sddm[1817]: Display server stopping...
May 11 12:29:40 linux-e1rt systemd-logind[1530]: **Failed to abandon session scope: Connection reset by peer**
May 11 12:29:41 linux-e1rt systemd[1]: **Failed unmounting /run/media/think_alone/show_other.**
May 11 12:29:41 linux-e1rt systemd[1]: **Failed unmounting /run/media/think_alone/serial2.**
May 11 12:29:41 linux-e1rt org.freedesktop.Tracker1[1983]: Received signal:15->'Terminated'
May 11 12:29:41 linux-e1rt org.freedesktop.Tracker1[1983]: OK
May 11 12:29:41 linux-e1rt iscsiadm[2775]: iscsiadm: No matching sessions found
May 11 12:29:41 linux-e1rt umount[2808]: umount: /run/media/think_alone/show_other: target is busy
May 11 12:29:41 linux-e1rt umount[2808]: (In some cases useful info about processes that
May 11 12:29:41 linux-e1rt umount[2808]: use the device is found by lsof(8) or fuser(1).)
May 11 12:29:41 linux-e1rt umount[2809]: umount: /run/media/think_alone/serial2: target is busy
May 11 12:29:41 linux-e1rt umount[2809]: (In some cases useful info about processes that
May 11 12:29:41 linux-e1rt umount[2809]: use the device is found by lsof(8) or fuser(1).)
May 11 12:29:41 linux-e1rt NetworkManager[1592]: <info> exiting (success)
May 11 12:29:41 linux-e1rt kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 11 12:29:41 linux-e1rt postfix/postfix-script[2832]: stopping the Postfix mail system
May 11 12:29:41 linux-e1rt postfix/master[1795]: terminating on signal 15
May 11 12:29:42 linux-e1rt SuSEfirewall2[2854]: Not unloading firewall rules at system shutdown
May 11 12:29:42 linux-e1rt ofonod[1501]: Terminating
May 11 12:29:42 linux-e1rt ofonod[1501]: **Aborting (signal 6) [/usr/sbin/ofonod]**
May 11 12:29:42 linux-e1rt kernel: **VBoxPciLinuxLinuxUnload**
May 11 12:29:42 linux-e1rt ofonod[1501]: **++++++++ backtrace ++++++++**
May 11 12:29:42 linux-e1rt vboxdrv[2776]: Stopping VirtualBox kernel modules..done
May 11 12:29:42 linux-e1rt ofonod[1501]: **#0 0x7f9f0e1ee120 in /lib64/libc.so.6**
May 11 12:29:42 linux-e1rt ofonod[1501]: **#1 0x7f9f0e1ee0a7 in /lib64/libc.so.6**
May 11 12:29:42 linux-e1rt ofonod[1501]: **#2 0x7f9f0e1ef458 in /lib64/libc.so.6**
May 11 12:29:42 linux-e1rt ofonod[1501]: **#3 0x7f9f0e795285 in /lib64/libdbus-1.so.3**
May 11 12:29:42 linux-e1rt ofonod[1501]: **#4 0x7f9f0e78bec1 in /lib64/libdbus-1.so.3**
May 11 12:29:42 linux-e1rt ofonod[1501]: **#5 0x7f9f0e783494 in /lib64/libdbus-1.so.3**
May 11 12:29:42 linux-e1rt ofonod[1501]: **#6 0x4814c4 in /usr/sbin/ofonod**
May 11 12:29:42 linux-e1rt ofonod[1501]: **#7 0x482dfd in /usr/sbin/ofonod**
May 11 12:29:42 linux-e1rt ofonod[1501]: **#8 0x485fa7 in ofono_debug() at ??:?**
May 11 12:29:42 linux-e1rt ofonod[1501]: **#9 0x411561 in /usr/sbin/ofonod**
May 11 12:29:42 linux-e1rt ofonod[1501]: **#10 0x7f9f0e1dab05 in /lib64/libc.so.6**
May 11 12:29:42 linux-e1rt ofonod[1501]: **+++++++++++++++++++++++++++**
May 11 12:29:45 linux-e1rt sddm[1817]: Removing display ":0" ...
May 11 12:29:45 linux-e1rt sddm[1817]: Adding new display on vt 7 ...
May 11 12:29:45 linux-e1rt sddm[1817]: Display server starting...
May 11 12:29:45 linux-e1rt sddm[1817]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{1b9a13c1-479d-4447-9f60-c2be3a1b4b5e} -
May 11 12:29:45 linux-e1rt kernel: **[drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting**
May 11 12:29:45 linux-e1rt kernel: **[drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BE5E (len 237, WS 0,**
May 11 12:29:45 linux-e1rt kernel: **[drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B674 (len 74, WS 0, **
May 11 12:29:45 linux-e1rt kernel: [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
May 11 12:29:45 linux-e1rt kernel: [drm] PCIE gen 3 link speeds already enabled
May 11 12:29:46 linux-e1rt kernel: **radeon 0000:01:00.0: Wait for MC idle timedout !**
May 11 12:29:46 linux-e1rt kernel: **radeon 0000:01:00.0: Wait for MC idle timedout !**
May 11 12:29:46 linux-e1rt kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000277000).
May 11 12:29:46 linux-e1rt kernel: radeon 0000:01:00.0: WB enabled
May 11 12:29:46 linux-e1rt kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xfff
May 11 12:29:46 linux-e1rt kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xfff
May 11 12:29:46 linux-e1rt kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xfff
May 11 12:29:46 linux-e1rt kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xfff
May 11 12:29:46 linux-e1rt kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xfff
May 11 12:29:46 linux-e1rt kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xfff
May 11 12:29:46 linux-e1rt display-manager[2793]: Shutting down service sddm..done
May 11 12:29:46 linux-e1rt kernel: **[drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)**
May 11 12:29:46 linux-e1rt kernel: **[drm:si_resume [radeon]] *ERROR* si startup failed on resume**
May 11 12:29:48 linux-e1rt sddm[1817]: Running display setup script "/etc/X11/xdm/Xsetup"
May 11 12:29:48 linux-e1rt sddm[1817]: Display server started.
May 11 12:29:48 linux-e1rt sddm[1817]: Socket server starting...
May 11 12:29:48 linux-e1rt sddm[1817]: Socket server started.
May 11 12:29:48 linux-e1rt sddm[1817]: Greeter starting...
May 11 12:29:48 linux-e1rt sddm[1817]: Adding cookie to "/run/sddm/{1b9a13c1-479d-4447-9f60-c2be3a1b4b5e}"
May 11 12:29:48 linux-e1rt sddm-helper[2917]: [PAM] Starting...
May 11 12:29:48 linux-e1rt sddm-helper[2917]: [PAM] Authenticating...
May 11 12:29:48 linux-e1rt sddm-helper[2917]: [PAM] returning.
May 11 12:29:48 linux-e1rt sddm[1817]: Display server stopping...
May 11 12:29:48 linux-e1rt sddm[1817]: Display server stopped.
May 11 12:29:48 linux-e1rt sddm[1817]: Running display stop script "/usr/share/sddm/scripts/Xstop"
May 11 12:29:48 linux-e1rt sddm[1817]: **Signal received: SIGTERM**
May 11 12:29:48 linux-e1rt sddm[1817]: Socket server stopping...
May 11 12:29:48 linux-e1rt sddm[1817]: Socket server stopped.
May 11 12:29:48 linux-e1rt sddm[1817]: Display server stopping...
May 11 12:29:48 linux-e1rt sddm-helper[2917]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
May 11 12:29:48 linux-e1rt sddm-helper[2917]: **pam_systemd(sddm-greeter:session): Failed to create session: Connection reset by pe**
May 11 12:29:48 linux-e1rt sddm-greeter[2920]: **QXcbConnection: Could not connect to display :1**
May 11 12:29:48 linux-e1rt sddm[1817]: Display server stopped.
May 11 12:29:48 linux-e1rt sddm[1817]: Running display stop script "/usr/share/sddm/scripts/Xstop"
May 11 12:29:48 linux-e1rt sddm[1817]: **QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.**
May 11 12:29:49 linux-e1rt systemd[1]: **Failed unmounting /boot.**
May 11 12:29:49 linux-e1rt kernel: **audit: type=1305 audit(1462953589.443:207): audit_pid=0 old=1296 auid=4294967295 ses=429496729**
May 11 12:29:49 linux-e1rt kernel: **audit: type=1131 audit(1462953589.443:208): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' c**
May 11 12:29:49 linux-e1rt auditd[1296]: The audit daemon is exiting.
May 11 12:29:49 linux-e1rt dracut-initramfs-restore[2923]: gzip: stdin: not in gzip format
May 11 12:29:49 linux-e1rt dracut-initramfs-restore[2923]: cpio: premature end of archive
May 11 12:29:49 linux-e1rt boot.apparmor[2934]: Unloading AppArmor profiles ..done
May 11 12:29:49 linux-e1rt umount[2977]: umount: /boot: target is busy
May 11 12:29:49 linux-e1rt umount[2977]: (In some cases useful info about processes that
May 11 12:29:49 linux-e1rt umount[2977]: use the device is found by lsof(8) or fuser(1).)
May 11 12:29:50 linux-e1rt kernel: **audit: type=1131 audit(1462953590.019:209): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' c**
May 11 12:29:50 linux-e1rt kernel: **audit: type=1130 audit(1462953590.891:210): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' c**
May 11 12:29:54 linux-e1rt systemd-cryptsetup[2935]: **Failed to deactivate: Device or resource busy**
May 11 12:29:54 linux-e1rt kernel: **audit: type=1130 audit(1462953594.047:211): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' c**
May 11 12:29:54 linux-e1rt kernel: **audit: type=1131 audit(1462953594.047:212): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' c**
May 11 12:29:54 linux-e1rt kernel: **audit: type=1131 audit(1462953594.047:213): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' c**
May 11 12:29:54 linux-e1rt kernel: **audit: type=1130 audit(1462953594.071:214): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' c**
May 11 12:29:54 linux-e1rt kernel: **watchdog watchdog0: watchdog did not stop!**
May 11 12:29:54 linux-e1rt ntfs-3g[1248]: **Unmounting /dev/sda10 (serial2)**
May 11 12:29:54 linux-e1rt ntfs-3g[1247]: **Unmounting /dev/sda9 (show_other)**
May 11 12:29:54 linux-e1rt systemd-journal[986]: Journal stopped
Someone has an idea to solve the problem?
and log
systemd-analyze critical-chain
~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @30.052s
└─**display-manager.service @14.920s +15.131s**
└─**systemd-user-sessions.service @14.847s +66ms**
└─basic.target @14.777s
└─timers.target @14.776s
└─systemd-tmpfiles-clean.timer @14.776s
└─sysinit.target @14.776s
└─**systemd-rfkill@rfkill1.service @17.911s +1ms**
└─system-systemd\x2drfkill.slice @7.019s
└─system.slice
└─-.slice
Yes and no. It is normal in case some service cannot be stopped right away and systemd waits until timeout before proceeding further. Now, of course service failing to stop should not be considered normal.
How do I find. the problem?
how to see log reboot?
Debugging shutdown issues is the most challenging. You may see something in logs of previous boot as suggested. You can also try to disable plymouth (splash screen) and remove “quiet” from kernel command line - in this case you will see messages about services start/stop during boot/shutdown. When service stop takes too much time, systemd starts to display sort of animation until timeout that also shows service name(s). It could be the easiest way in this case.
how to disable plymouth (splash screen) and remove “quiet” from kernel?
For a one time test at boot press e find line starting linux or linuxefi then follow nose remove quiet, press F10 to continue boot. For permanent modify in Yast boot loader
Thanks ,I’ve tested a bit different
but,I wrote two. simple scripts And I’ll add it to menu editor
I used those commands for shutdown and reboot
sudo shutdown -h now
sudo shutdown -r now
I using scripts for reboot
Now,the system is quick shutdown and reboot