Hassio 94.1 - won't restart, no log created, and it can't find configuration.yaml

Updated from 93.1 to 94.1 today and it was working great. Now it won’t start. The errors are baffling.
check config fails because it says it can’t find configuration.yaml, but then says there was a successful/partial config. No log file is created after attempting to start hassio, even with default logging set to debug.

hassio ha check
Error: Testing configuration at /config
Failed config
General Errors:
- File not found: /config/configuration.yaml
Successful config (partial)

config ls -l configuration.yaml
-rw-r–r-- 1 root root 11290 Jun 9 18:29 configuration.yaml

config hassio ha start
Error: Unknown Error, see logs

config ls home-assistant.log
ls: home-assistant.log: No such file or directory

Raspi3 B+, with 23.7G free sdcard space.

Before I rebooted the log contained this error:

2019-06-09 14:52:04 ERROR (MainThread) [frontend.js.latest.201906040] https://xxxxxx.duckdns.org:8123/frontend_latest/app.29ef27ad.js:2:59869 Uncaught TypeError: Cannot convert undefined or null to object
2019-06-09 14:52:04 ERROR (MainThread) [frontend.js.latest.201906040] https://xxxxxx.duckdns.org:8123/frontend_latest/app.29ef27ad.js:2:59869 Uncaught TypeError: Cannot convert undefined or null to object
2019-06-09 17:22:43 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connection
2019-06-09 17:57:21 ERROR (MainThread) [homeassistant.components.hassio] File not found: /config/configuration.yaml

Had hoped a reboot would clear it. If this were a corrupt SDCard situation, then it would seem that I would not be able to edit configuration.yaml, which through ssh and vi, seems to be perfectly fine.

I would greatly appreciate any troubleshooting advice before attempting a complete wipe and rebuild. Thanks!

Perhaps one of the files that you load with the !include statement is missing or corrupt? Such as automations.yaml, scripts.yaml, etc…, I have around 6 !include statements in my configuration.yaml.

2 Likes

Thanks so much! I had an old scripts.yaml that contained scripts that were no longer needed, so I removed it. But configuration.yaml still had the !include scripts.yaml which really messed things up good.

Would be a good enhancement request to check if an include file doesn’t exist then issue a reasonable warning and move on.

EDIT: Decided this was better referenced as a bug than a feature to correct how a missing include is handled. Issue #24446 submitted.

2 Likes

Thanks for that.
Regards Christian .

Hi I’m getting the exact same error as you, here’s an entry from my log:

2019-06-27 20:56:29 ERROR (MainThread) [frontend.js.latest.201906040] http://hassio.local:8123/frontend_latest/app.29ef27ad.js:2:59869 TypeError: can't convert undefined to object
2019-06-27 20:56:29 ERROR (MainThread) [frontend.js.latest.201906040] http://hassio.local:8123/frontend_latest/app.29ef27ad.js:2:59869 TypeError: can't convert undefined to object
2019-06-27 20:56:29 ERROR (MainThread) [frontend.js.latest.201906040] http://hassio.local:8123/frontend_latest/app.29ef27ad.js:2:59869 TypeError: can't convert undefined to object

Can I ask how you tracked down the missing file?

I have over 100 !include files and can not see an easy way to find which !include is causing the issue for me! :frowning:

Also my log didn’t have the:

File not found: /config/configuration.yaml

In my log, very odd.

Those TypeErrors I had included in my original post are totally unrelated to the issue I was having with Hassio not restarting. That problem was due to a missing include file. At the time of my post, I did not know they were unrelated.

I have since found that this TypeError was only occurring with Chrome, accessing certain HA links, like History. According to this post the problem was found and the fix was merged several days ago. I assume the fix is in .95.0 now

1 Like

Thanks very much for the update :slight_smile:

Often finding out what causes these errors is like finding a needle in a haystack.

I seem to be getting less of these messages now, and my system is stable, so I’m not going to tinker just yet.