Attempts to reboot using standard tooling (reboot, shutdown, systemctl) failed with timeouts while trying to talk to the init daemon. Investigation showed systemd was PID 1, but its DBus name org.freedesktop.systemd1 was not owned on the system bus and DBus activation attempts timed out. This prevented systemctl and logind from reaching reboot.target.
sudo reboot now / sudo reboot:
Call to Reboot failed: Connection timed outFailed to talk to init daemon: Connection timed outsystemd:
/usr/lib/systemd/systemd --system ...org.freedesktop.systemd1 appears as activatable on DBus, but not owned:
systemctl calls fail:
Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)systemd-logind reports:
Failed to get load state of reboot.target: ... timed outsystemd-journald repeatedly logs:
Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected/proc/1/stack shows PID 1 blocked in do_wait/waitid at time of capture.systemctl-mediated operations and clean reboot/shutdown path were impaired.If the system must be rebooted while systemd is unresponsive on DBus, use a forced reboot path (after a sync) that bypasses DBus/systemd control-plane.
systemd DBus name is owned:
busctl --system list | rg systemd1systemctl is-system-running works normally.journalctl -b -1 -p warning..alert --no-pager | lesscat /proc/1/stackjournalctl -b --no-pager | rg -i '(systemd1|dbus|watchdog|logind)' | tail -n 300