Arch Linux

Stalafin

Member

From: Berlin, Germany

Registered: 2007-10-26

Posts: 617

Can't shutdown, poweroff: machines reboots instead

No matter which commands I use, systemctl poweroff, shutdown -h, halt -p, my machine will immediately reboot instead. Here are all journalctl lines immediately after calling systemctl poweroff: the system will tell me that it is going to shutdown, but instead it reboots. Also, the last message I see before the reboot occurs is along the lines of “rebooting now”.

Nov 08 13:46:04 rechenschieber systemd-logind[335]: System is powering down.
Nov 08 13:46:04 rechenschieber org.a11y.atspi.Registry[836]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async rea
Nov 08 13:46:04 rechenschieber polkitd[424]: Unregistered Authentication Agent for unix-process:888:1773 (system bus name :1.13, object path /org/freedesktop/PolicyKit1/Authentic
Nov 08 13:46:04 rechenschieber org.a11y.Bus[769]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-err
Nov 08 13:46:04 rechenschieber systemd[609]: Stopping Default.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopped target Default.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopping Basic System.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopped target Basic System.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopping Paths.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopped target Paths.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopping Timers.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopped target Timers.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopping Sockets.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopped target Sockets.
Nov 08 13:46:04 rechenschieber systemd[609]: Starting Shutdown.
Nov 08 13:46:04 rechenschieber systemd[609]: Reached target Shutdown.
Nov 08 13:46:04 rechenschieber systemd[609]: Starting Exit the Session...
Nov 08 13:46:04 rechenschieber rpcbind[399]: rpcbind terminating on signal. Restart with "rpcbind -w"
Nov 08 13:46:04 rechenschieber NetworkManager[331]: <warn> disconnected by the system bus.
Nov 08 13:46:04 rechenschieber NetworkManager[331]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-e
Nov 08 13:46:04 rechenschieber systemd[609]: Received SIGRTMIN+24 from PID 897 (kill).
Nov 08 13:46:04 rechenschieber systemd[611]: pam_unix(systemd-user:session): session closed for user janis
Nov 08 13:46:04 rechenschieber systemd[1]: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 08 13:46:04 rechenschieber systemd[1]: Unit rpcbind.service entered failed state.
Nov 08 13:46:04 rechenschieber systemd[1]: rpcbind.service failed.
Nov 08 13:46:05 rechenschieber NetworkManager[331]: <info> caught signal 15, shutting down normally.
Nov 08 13:46:05 rechenschieber NetworkManager[331]: <info> (wlan0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Nov 08 13:46:05 rechenschieber NetworkManager[331]: ** (NetworkManager:331): CRITICAL **: dbus_g_proxy_call_no_reply: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Nov 08 13:46:05 rechenschieber NetworkManager[331]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Nov 08 13:46:05 rechenschieber kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 08 13:46:05 rechenschieber wpa_supplicant[536]: Successfully initialized wpa_supplicant
Nov 08 13:46:05 rechenschieber wpa_supplicant[536]: wlan0: CTRL-EVENT-TERMINATING
Nov 08 13:46:05 rechenschieber kernel: e1000e: eth0 NIC Link is Down
Nov 08 13:46:05 rechenschieber kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 08 13:46:05 rechenschieber NetworkManager[331]: (NetworkManager:331): GLib-CRITICAL **: Source ID 37 was not found when attempting to remove it
Nov 08 13:46:05 rechenschieber NetworkManager[331]: <info> exiting (success)
Nov 08 13:46:05 rechenschieber umount[981]: umount: /var: target is busy
Nov 08 13:46:05 rechenschieber umount[981]: (In some cases useful info about processes that
Nov 08 13:46:05 rechenschieber umount[981]: use the device is found by lsof(8) or fuser(1).)
Nov 08 13:46:05 rechenschieber systemd[1]: var.mount mount process exited, code=exited status=32
Nov 08 13:46:05 rechenschieber systemd[1]: Failed unmounting /var.
Nov 08 13:46:05 rechenschieber systemd[1]: Shutting down.
Nov 08 13:46:05 rechenschieber systemd-journal[141]: Journal stopped
-- Reboot --

I tried following up on several suggestions I found around here and online: I disabled Wake-on-Lan in the BIOS, I disabled/stopped tlp.service and tpfand.service (the only power-management-like tools I am running). But that does not help.

Note: the system is not powering off to then reboot. It reboots immediately, just as if I had executed `systemctl reboot'.

FWIW, my system is up to date:

3.17.2-1-ARCH #1
systemd 217

Any fixes? It's getting a bid annoying having to shut down the machine through the syslinux menu after each of these reboots.

Last edited by Stalafin (2014-11-08 12:59:53)

Potomac

Member

Registered: 2011-12-25

Posts: 551

Re: Can't shutdown, poweroff: machines reboots instead

in your log we can read this :

rpcbind.service failed
 umount: /var: target is busy
Failed unmounting /var

it's not normal, you could try to solve these errors, it may help to solve the shutdown problem,

use "systemctl --failed --all" at boot in order to know if all is Ok at startup

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,111

Website

Re: Can't shutdown, poweroff: machines reboots instead

Fixed by:

http://cgit.freedesktop.org/systemd/sys … 53b43ee992

---

blog | ±github