Arch Linux

tarask

Member

Registered: 2017-09-29

Posts: 3

Long shutdown (probably systemd issue)

Hi all,

I'm using Arch Linux with KDE plasma 5.

After systemd update to version 234.11-9 couple days ago, I'm getting a problem with long shutdown/reboot process. I've found similar issue on this forum here and on Git Hub

In journalctl several 'Stopping' time out messages

вер 29 13:56:26 archlinux systemd[515]: at-spi-dbus-bus.service: State 'stop-sigterm' timed out. Killing.
вер 29 13:56:26 archlinux systemd[515]: at-spi-dbus-bus.service: Killing process 766 (at-spi-bus-laun) with signal SIGKILL.
вер 29 13:56:26 archlinux systemd[1]: session-c1.scope: Stopping timed out. Killing.
вер 29 13:56:26 archlinux systemd[1]: session-c1.scope: Killing process 1168 (speech-dispatch) with signal SIGKILL.
вер 29 13:56:26 archlinux systemd[1]: session-c1.scope: Killing process 5215 (sd_dummy) with signal SIGKILL.
вер 29 13:56:26 archlinux systemd[515]: at-spi-dbus-bus.service: Main process exited, code=killed, status=9/KILL
вер 29 13:56:26 archlinux systemd[515]: Stopped Accessibility services bus.
вер 29 13:56:26 archlinux systemd[515]: at-spi-dbus-bus.service: Unit entered failed state.
вер 29 13:56:26 archlinux systemd[515]: at-spi-dbus-bus.service: Failed with result 'timeout'.

вер 29 13:57:06 archlinux systemd[1]: sddm.service: State 'stop-final-sigterm' timed out. Killing.
вер 29 13:57:06 archlinux systemd[1]: sddm.service: Killing process 365 (Xorg) with signal SIGKILL.
вер 29 13:58:37 archlinux systemd[1]: sddm.service: Processes still around after final SIGKILL. Entering failed mode.

вер 29 14:00:07 archlinux systemd[1]: NetworkManager.service: State 'stop-sigterm' timed out. Killing.
вер 29 14:00:07 archlinux systemd[1]: NetworkManager.service: Killing process 295 (NetworkManager) with signal SIGKILL.
вер 29 14:00:07 archlinux systemd[1]: wpa_supplicant.service: State 'stop-sigterm' timed out. Killing.
вер 29 14:00:07 archlinux systemd[1]: wpa_supplicant.service: Killing process 333 (wpa_supplicant) with signal SIGKILL.
вер 29 14:01:37 archlinux systemd[1]: NetworkManager.service: Processes still around after SIGKILL. Ignoring.
вер 29 14:01:37 archlinux systemd[1]: wpa_supplicant.service: Processes still around after SIGKILL. Ignoring.
вер 29 14:03:07 archlinux systemd[1]: NetworkManager.service: State 'stop-final-sigterm' timed out. Killing.
вер 29 14:03:07 archlinux systemd[1]: NetworkManager.service: Killing process 295 (NetworkManager) with signal SIGKILL.
вер 29 14:03:07 archlinux systemd[1]: wpa_supplicant.service: State 'stop-final-sigterm' timed out. Killing.
вер 29 14:03:07 archlinux systemd[1]: wpa_supplicant.service: Killing process 333 (wpa_supplicant) with signal SIGKILL.
вер 29 14:04:37 archlinux systemd[1]: NetworkManager.service: Processes still around after final SIGKILL. Entering failed mode.
вер 29 14:04:37 archlinux systemd[1]: Stopped Network Manager.
вер 29 14:04:37 archlinux systemd[1]: NetworkManager.service: Unit entered failed state.
вер 29 14:04:37 archlinux systemd[1]: NetworkManager.service: Failed with result 'timeout'.
вер 29 14:04:37 archlinux systemd[1]: wpa_supplicant.service: Processes still around after final SIGKILL. Entering failed mode.
вер 29 14:04:37 archlinux systemd[1]: Stopped WPA supplicant.
вер 29 14:04:37 archlinux systemd[1]: wpa_supplicant.service: Unit entered failed state.
вер 29 14:04:37 archlinux systemd[1]: wpa_supplicant.service: Failed with result 'timeout'.

After all of that it takes around 10 mins to shutdown the system.

I tried a workaround with "/etc/sysctl.d/50-coredump.conf" file, it didn't help

Does anybody else experiencing the issue? How it can be fixed?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,435

Re: Long shutdown (probably systemd issue)

Unlikely, that update didn't change anything that would be causing this. If it worked with 234.11-8 it works the same with 234.11-9

What "workaround" did you try? Why are all your services failing to quit? Check your journal is there any common information? If you disabled coredumps and you would be getting coredumps, reenable coredumps and examine them