Skip to main content
Server Fault

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • I'm also using openSuse 13.2 and have the same problem, but kill -9 doesn't work in my case, as systemd seems to ignore it. Using systemctl daemon-reexec instead restarts it (and is the only systemctl operation that doesn't time out), but with the same parameters, so I keep getting the timeouts afterwards. Any idea how to force it? I can't tell from the link you posted to the other thread if this is strictly required when using initramfs. Commented Mar 8, 2016 at 22:00
  • 9
    Neither kill -9 1 or systemctl daemon-reexec worked for me so I resorted to the big red switch that is reboot. But that did not work! (Failed to start reboot.target: Failed to activate service 'org.freedesktop.systemd1': timed out. See system logs and 'systemctl status reboot.target' for details. Failed to open /dev/initctl: No such device or address. Failed to talk to init daemon.) After a bit of googling I found systemctl --force --force reboot (ubuntuforums.org/…) did a reboot and appears to be back to normal Commented Mar 29, 2018 at 13:26
  • It worked for me on elementaryOS loki, got stuck after configuring TightVNC server, but now it works like a charm. Commented Sep 24, 2018 at 16:28
  • None of all the above worked for me. Commented Jul 26, 2019 at 2:27
  • 1
    I am getting this issue and it becomes really annoying. Neither kill -9 1 or systemctl daemon-reexec worked. The only solution if found working is the reboot double forced but after 2 days, the problem is back ! Commented Sep 9, 2020 at 12:26