How to cleanly reboot core OS when "Failed to talk to init daemon" is seen?

coreos
Rajesh picture Rajesh · May 14, 2016 · Viewed 24.4k times · Source

How do I cleanly reboot my coreOS after the following issue shows up?

core@node2 ~ $ sudo reboot
Failed to talk to init daemon
core@node2 ~ $ sudo shutdown -r now
Failed to talk to init daemon.
core@node2 ~ $ sudo systemctl reboot
Failed to get D-Bus connection: Operation not permitted
core@contiv-node2 ~ $ shutdown
Must be root.
core@node2 ~ $ sudo shutdown
Unable to perform operation without bus connection.
core@node2 ~ $ cat /etc/lsb-release 
DISTRIB_ID=CoreOS
DISTRIB_RELEASE=991.2.0
DISTRIB_CODENAME="Coeur Rouge"
DISTRIB_DESCRIPTION="CoreOS 991.2.0 (Coeur Rouge)"

Answer

Christophe Schmitz picture Christophe Schmitz · May 14, 2016 
sudo reboot -f

-f, --force Force immediate halt, power-off, reboot. Do not contact the init system.

Related questions

How to retry image pull in a kubernetes Pods?

I am new to kubernetes. I have an issue in the pods. When I run the command kubectl get pods Result: NAME READY STATUS RESTARTS AGE mysql-apim-db-1viwg 1/1 Running 1 20h mysql-govdb-qioee 1/1 Running 1 20h mysql-userdb-l8q8c 1/1 Running 0 20h wso2am-default-813…

Read More
Postgres - testing database connection in bash

I wonder if there is an alternative to the psql command to test the connection to a postgresql database using bash. I'm setting up a Core OS cluster and have a side service which should perform the equivalent of psql …

Read More
Docker container logs taking all my disk space

I am running a container on a VM. My container is writing logs by default to /var/lib/docker/containers/CONTAINER_ID/CONTAINER_ID-json.log file until the disk is full. Currently, I have to delete manually this file to …

Read More