15 Apr
2018
15 Apr
'18
10:07 a.m.
If dbus is dead, but systemd is alive, you can
kill -SIGRTMIN+4 1 # clean shutdown
or
kill -SIGRTMIN+14 1 # expedited shutdown
If systemd is catatonic, you can
systemctl -ff poweroff
which will sync and poweroff but leave your filesystems marked dirty so
you'll get a fsck on next boot. In other words, slightly nicer than a
xen destroy. (If you prefer to avoid the fsck, you could probably
remount your rootfs read-only, but I expect you'd have to kill off a
bunch of processes by hand first.)
Ref: https://github.com/systemd/systemd/issues/3282
Ross
On 15/04/18 20:54, Andy Ransom wrote:
Hi,
Having run what appears to be a successful upgrade from Ubuntu 14.04 to
16.04 (yes, yes I know living in the past) I've hit a problem.
My VPS won't reboot.
$ sudo shutdown -r now
Gives:
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.
Couldn't find an alternative telinit implementation to spawn.
failed to run telinit 6 for upstart fallback
Failed to talk to init daemon.
and trying to shut down via the xen console I get:
xen-shell> shutdown
Shutting down instance: <vpsname>
Shutting down domain <number>
Waiting for 1 domains
and the VPS stays up.
Any suggestions before I hit it with a xen console "destroy"?
Andy
--
Andrew Ransom
<aransom(a)gmail.com>
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users