Supervisor won't load on HassOS?

[kareem613]

This isn’t directly after an update so I don’t know what caused it. I just woke up one morning and HA was down. Couldn’t SSH in either. Logged in directly on the machine (VM).
VM was created directly from the official image.

Any action I take fails. ex.
supervisor info
result in
Get http://supervisor/supervisor/info: dial tcp 172.30.32.2:80 connect: no route to host

and core info
results in
Get http://supervisor/core/info: dial tcp 172.30.32.2:80 connect: no route to host
Any attempts to reload or start result in similar messages.

Is this the supervisor dead? I can’t tell what the issue is or how to resolve it.

[VDRainer]

VirtualBox on Windows 10?

Help with network or docker setup when installing Hassio on Windows with VirtualBox

Hi All, Been working on a problem with hassio that occurred last Wednesday. After a reboot of hassio virtual machine in VirtualBox my homeassistant installation didn’t come online (as in I couldn’t reach it via web-interface). Tried a proper shutdown and reboot a couple of times, but it didn’t help. The first thing to do? Read the logs of course. But the only thing it said, was that it took longer than x second to set up this and that. The second step to do? To the forum. Browsing the forum g…

[kareem613]

No. Synology DSM.

[JM123]

Were you able to find a solution to this? I had the same problem. Running on VirtualBox on OSX. Finally gave up and completely rebuilt from scratch–not even using an old backup. A few days later, I shutdown the host computer, and here I am back to the same problem… Sounds like it might be related to the supervisor which automatically updates itself?

[kareem613]

I never figured it out. Moved everything over to proxmox and haven’t had an issue since.

[kctx]

I had this same problem:

@kareem613

http://supervisor/supervisor/info: dial tcp 172.30.32.2:80 connect: no route to host

Ultimately, the fix was this, prior to a reboot:

rm /mnt/data/docker/network/files/local-kv.db

If I rebooted without removing the file, I was stuck in a boot-loop. I was able to restore a VM snapshot and investigated for hours.

Manually trying to restart the supervisor docker container would give the error above. It was telling to look at a running system and see the output of docker network list, docker network inspect hassio and docker container inspect hassio_supervisor compared to the same commands on my failing system.

The network inspect showed a latent “endpoint” related to a prior run of hassio_supervisor. I found no way to clean up the metadata, other than to delete the local-kv.db file.