HA wont start but process is running

Configuration
1

So just out of nowhere HA stoped working.
I had upgraded to 0.86 the day before and everything went fine and then I couldn’t access the web UI anymore. I just get

Unable to connect to Home Assistant.
Retry

I have tried to upgrade to the latest, 0.86.4 but no difference.
The process is running:

/srv/homeassistant/bin/python3 /srv/homeassistant/bin/hass -c /home/homeassistant/.homeassistant

Nothing is written to home-assistant.log and I used to get a bunch of messages there when restarting the HA service.

I’m runnning on a Raspberry Pi running Raspbian.
I can’t figure out whats wrong here…

I have tried to comment out a bunch of stuff in my config file but there’s no difference.
If I change name of automations.yaml I get this in the log:

ERROR (MainThread) [homeassistant.bootstrap] Error loading /home/homeassistant/.homeassistant/configuration.yaml: Config file not found: /home/homeassistant/.homeassistant/automations.yaml

But that’s the only thing I can get it to log.

What should I try next?

If I woulnd’t have been runnning Z-Wave on this I could just do a reinstallation of it but I just dont have the time to be running around and exclude/include all devices again…

Any help is appreciated.

2

I am relatively new to HASS so I dont have a solution to your problem, but you do not need to rebuild your z-wave network. Just save/copy the zwcfg_*.xml file and restore it afterwards and you are good to go.

3

try

$ systemctl status [email protected]

to see the state of the service.

And just to check a wild idea, try

df -h

to check if you have some disk space left.

4

By any chance do you have:

discovery:

section in your configuration.yaml?
Try commenting it out and restart HA
I had something like this couple weeks back and it appears that there are some parts that don’t have timeout set and cause HA to wait forever (in my case it was discovering of Chromecast devices IIRC).

5 
pi@raspberrypi:/home/homeassistant/.homeassistant $ sudo systemctl status home-assistant@homeassistant
● [email protected] - Home Assistant
   Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-01-30 21:53:29 CET; 27s ago
 Main PID: 7416 (hass)
   CGroup: /system.slice/system-home\x2dassistant.slice/[email protected]
           └─7416 /srv/homeassistant/bin/python3 /srv/homeassistant/bin/hass -c /home/homeassistant/.homeassistant

Jan 30 21:53:29 raspberrypi systemd[1]: Started Home Assistant.
Jan 30 21:53:33 raspberrypi hass[7416]: 2019-01-30 21:53:33 INFO (Thread-5) [homeassistant.config] Upgrading configuration directory from  to 0.86.4
Jan 30 21:53:33 raspberrypi hass[7416]: Config directory: /home/homeassistant/.homeassistant

I got plenty of disk space left. 42% used on the root partition.

discovery: is not used.

Can’t figure out what to do next…

6

That all looks good. I would move your configuration aside and restart HA so it will create a new one, to see if it likes that.

7

Turns out there is a hidden file called .HA_VERSION that for some reason was empty.
I put the text 0.86.4 into it and it started up like normal.

Don’t know why or when this happened since it worked after I upgraded to 0.86…

8

That is something new to me. I have the file as well. Where did you get that info from?

9

I was just looking around. Then I made HA start in a new empty folder and let it create all the neccesary files and it started just like a new instance. Then I compared the files and noticed the hidden file and that it was empty in my first config folder.

2 Likes