HA will no longer start

hottl · January 15, 2021, 4:15pm

I have been running HA within Docker / Portainer on a NUC10i7 with Ubuntu 20.04 for a couple of weeks and all started out fine. But today my HA wouldn’t load within my browser, either through the duckdns address or via the LAN IP.

When I log in to the NUC via VNC I see that all but one containers is running; I tried to start the last one, but although is starts, when I refresh the page it is stopped again. Rebooting the NUC doesn’t help.

Where is my problem going to lie? Is it a problem that the addon_core_check_config is stopped? I’m very new to Linux in general, and am not sure where to troubleshoot - within HA itself, with Docker, with Portainer, with Ubuntu or where?

Although I can VNC in to the NUC, I can’t ssh through the Terminal on my Mac (I don’t think that I ever set it up).

TIA

m0wlheld · January 15, 2021, 6:20pm

I don‘t now how Home Assistant OS is designed, but according to the Published Ports there‘s nothing listening on port 8123 or 80.

Did you check the logs of the homeassistant container (left icon in Quick Actions)?

(Btw: Why do you use VNC to open Portainer‘s web-interface?)

hottl · January 15, 2021, 7:00pm

Thanks @m0wlheld ; Frustratingly I can’t get in to home assistant at all, so can’t check the logs (or at least I don’t know how to). Neither routing via the duckdns address nor via the local IP works (but did before).

I use VNC on my Mac as it never occurred to me that I could just access it through the browser on my laptop. But your comment made me try it and it works! (Portainer, that is, not Home Assistant)>

m0wlheld · January 15, 2021, 7:12pm

Using the Portainer interface (which you obviously can access), click the “paper” icon in the Quick Actions column next to the Home Assistant Container.

grafik

hottl · January 15, 2021, 8:23pm

Thanks again. There is a load of similar errors, the last few of which are …


2021-01-15 20:03:19 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds
2021-01-15 20:04:42 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds
2021-01-15 20:04:42 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds
2021-01-15 20:06:05 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds
2021-01-15 20:06:05 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds
2021-01-15 20:07:28 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds
2021-01-15 20:07:28 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds
2021-01-15 20:08:51 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds
2021-01-15 20:08:51 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds
2021-01-15 20:10:14 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds
2021-01-15 20:10:14 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds

Now that I see this, HA may have “gone wrong” just as I did a firmware update on one of my Shelly1 devices via their webpage - maybe it went wrong somehow? Anyway, I have just rebooted (via the browser) all 6 of my Shelly1’s, but that hasn’t stopped the errors continuing.

Can one read in to the pairs of errors that two Shelly devices have gone wrong, or is there a way to nuke the entire Shelly Integration within HA via Portainer in order to rescue the rest of the setup? If so, how might I access it?

TIA

hottl · January 15, 2021, 8:43pm

Looking further back in the error report, back to when I think that I turned the NUC off & on again using the power button (not friendly, I know ), does anything show up here as a potential cause of my woes?

NB: Roon and Roon ROCK refer to my music server (on another NUC). I do have a fairly recent HA Snapshot on my laptop, but wouldn’t know if it is possible to somehow re-inject it without being able to access the HA GUI…

2021-01-15 16:41:01 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 80 seconds,
[cont-finish.d] executing container finish scripts...,
[cont-finish.d] done.,
[s6-finish] waiting for services.,
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening,
[s6-finish] sending all processes the TERM signal.,
[s6-finish] sending all processes the KILL signal and exiting.,
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.,
[s6-init] ensuring user provided files have correct perms...exited 0.,
[fix-attrs.d] applying ownership & permissions fixes...,
[fix-attrs.d] done.,
[cont-init.d] executing container initialization scripts...,
[cont-init.d] udev.sh: executing... ,
[18:10:49] INFO: Update udev information,
[cont-init.d] udev.sh: exited 0.,
[cont-init.d] done.,
[services.d] starting services,
[services.d] done.,
2021-01-15 18:10:51 WARNING (MainThread) [homeassistant.components.http] The 'base_url' option is deprecated, please remove it from your configuration,
2021-01-15 18:11:01 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.,
2021-01-15 18:11:02 WARNING (SyncWorker_5) [homeassistant.util.yaml.loader] YAML file /config/ip_bans.yaml contains duplicate key "192.168.2.1". Check lines 1 and 4,
2021-01-15 18:11:02,714 INFO   roonapi -- Connecting to Roon server 192.168.2.49:9100,
2021-01-15 18:11:02 INFO (MainThread) [roonapi] Connecting to Roon server 192.168.2.49:9100,
2021-01-15 18:11:02,725 INFO   roonapi -- Connection with roon websockets (re)created.,
2021-01-15 18:11:02,725 INFO   roonapi -- Confirming previous registration with Roon...,
2021-01-15 18:11:02 INFO (Dummy-6) [roonapi] Connection with roon websockets (re)created.,
2021-01-15 18:11:02 INFO (Dummy-6) [roonapi] Confirming previous registration with Roon...,
2021-01-15 18:11:02,727 INFO   roonapi -- Registered to Roon server Roon ROCK,
2021-01-15 18:11:02 INFO (Thread-3) [roonapi] Registered to Roon server Roon ROCK,
2021-01-15 18:11:02 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]: required key not provided @ data['action'][0]['domain']. Got None,
required key not provided @ data['trigger'][0]['platform']. Got None. (See /config/configuration.yaml, line 9). ,
2021-01-15 18:11:02 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]: Unexpected value for condition: 'None'. Expected numeric_state, state, sun, template, time, zone, and, or, not, device @ data['condition'][0]. Got None,
Unexpected value for condition: 'None'. Expected numeric_state, state, sun, template, time, zone, and, or, not, device @ data['condition'][1]. Got None. (See /config/configuration.yaml, line 9). ,
2021-01-15 18:11:02 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]: extra keys not allowed @ data['action'][0]['brightness_pct']. Got None,
extra keys not allowed @ data['action'][0]['domain']. Got None,
extra keys not allowed @ data['action'][0]['type']. Got None,
required key not provided @ data['trigger'][2]['platform']. Got None. (See /config/configuration.yaml, line 9). ,
2021-01-15 18:11:06 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 5 seconds,
2021-01-15 18:11:06 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 5 seconds,
2021-01-15 18:11:14 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 10 seconds,
2021-01-15 18:11:14 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 10 seconds,
2021-01-15 18:11:27 WARNING (MainThread) [homeassistant.config_entries] Config entry for shelly not ready yet. Retrying in 20 seconds,

EDITED TO ADD: Interestingly, HA itself still seems to be working (lights going off & on according to the schedule), but I can’t access it / interact with it via the browser.

Nick4 · January 16, 2021, 10:56am

Can’t help you with your current problem but wanted to give you a tip: Proxmox VE
With this you can run containers and virtual machines without having a full OS underneath like you do now & you make 2 layers (ubuntu + portainer) into 1 by just having Proxmox.
On top of that, if your Linux skills are basic, this could be easier to manage.
You get quite a lot of different advantages with it as well like easy way to take backups & snapshots.

hottl · January 16, 2021, 11:40am

By way of an update, it seems like a rogue ip_bans.yaml file had been created yesterday evening, and now that I have been able to delete it the Home Assistant GUI is now working again. Thanks for your help above - I’ve learned several new skills with this issue, so much appreciated !