I’m getting an error after updating

davisstewart · February 6, 2021, 1:31pm

After updating to Home Assistant 2021.2.0, HA is stuck and wont restart fully.

Node Red,File Editor & Dropbox Upload addons will not start automatically. They have to be started manually. Can’t update to Home Assistant Core 2021.2.1 as I get 21-02-06 09:55:50 ERROR (MainThread) [supervisor.utils] Can’t execute wrapper while a task is in progress
System Health

version: core-2021.2.0
installation_type: Home Assistant OS
dev: false
hassio: true
docker: true
virtualenv: false
python_version: 3.8.7
os_name: Linux
os_version: 5.4.79-v7l
arch: armv7l
timezone: Europe/Dublin

logged_in: false
can_reach_cert_server: ok
can_reach_cloud_auth: ok
can_reach_cloud: ok

host_os: Home Assistant OS 5.10
update_channel: stable
supervisor_version: supervisor-2021.01.7
docker_version: 19.03.13
disk_total: 116.5 GB
disk_used: 9.8 GB
healthy: true
supported: true
board: rpi4
supervisor_api: ok
version_api: ok
installed_addons: Samba share (9.3.0), deCONZ (6.6.4), File editor (5.2.0), Check Home Assistant configuration (3.6.0), Terminal & SSH (8.10.0), Google Assistant SDK (2.5.0), Dropbox Upload (1.2.11), JupyterLab Lite (0.3.1), Node-RED (8.0.1), Mosquitto broker (5.1), TasmoAdmin (0.14.0), Home Panel (1.8.3), Z-Wave JS (0.1.4), Portainer (1.4.0)

dashboards: 1
resources: 5
views: 8
mode: storage

These are my Logs, any help would be appreciated.

2021-02-05 20:33:24 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.

2021-02-05 20:33:45 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=106 from 2021-02-05 15:25:02.006123)

2021-02-05 20:33:50 ERROR (MainThread) [homeassistant.components.panel_custom] Unable to register panel ZWave Graph: Either js_url, module_url or html_url is required.

2021-02-05 20:33:54 WARNING (MainThread) [zwave_js_server] Connected to a Zwave JS Server with an untested version, you may run into compatibility issues!

2021-02-05 20:33:57 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.

2021-02-05 21:13:01 WARNING (Thread-8) [pychromecast.socket_client] [TV Living Room(192.xxx.xxxxx):8009] Heartbeat timeout, resetting connection

2021-02-05 21:13:20 ERROR (Thread-8) [pychromecast.socket_client] [TV Living Room(192.xxx.x.xxx):8009] Failed to connect to service Chromecast-db4d49562d2917bfa162d50d8cc659ca._googlecast._tcp.local., retrying in 5.0s

2021-02-05 23:39:54 WARNING (Thread-8) [pychromecast.socket_client] [TV Living Room(192.xxx.x.xx):8009] Heartbeat timeout, resetting connection

2021-02-05 23:40:24 ERROR (Thread-8) [pychromecast.socket_client] [TV Living Room(192.xxx.x.x):8009] Failed to connect to service Chromecast-db4d49562d2917bfa162d50d8cc659ca._googlecast._tcp.local., retrying in 5.0s

2021-02-06 02:18:56 WARNING (Thread-7) [pychromecast.socket_client] [Kitchen speaker(192.xxxxx):8009] Heartbeat timeout, resetting connection

2021-02-06 02:52:41 ERROR (Thread-10) [pychromecast.socket_client] [All speakers(192.xxx.x.x):32020] Error reading from socket.

2021-02-06 02:52:41 WARNING (Thread-10) [pychromecast.socket_client] [All speakers(192.xx.x.x):32020] Error communicating with socket, resetting connection

2021-02-06 02:52:41 ERROR (Thread-10) [pychromecast.socket_client] [All speakers(192.xxx.x.x):32020] Failed to connect to service Google-Cast-Group-6aed0016802f4e44b11f0b286843e393-1._googlecast._tcp.local., retrying in 5.0s

2021-02-06 02:53:11 WARNING (Thread-9) [pychromecast.socket_client] [Office speaker(192.xxxx.x):8009] Heartbeat timeout, resetting connection

2021-02-06 02:53:25 ERROR (Thread-10) [pychromecast.socket_client] [All speakers(192.xxx.x.x):32020] Error reading from socket.

2021-02-06 02:53:25 WARNING (Thread-10) [pychromecast.socket_client] [All speakers(192.xxx.x.x):32020] Error communicating with socket, resetting connection

2021-02-06 02:53:25 ERROR (Thread-10) [pychromecast.socket_client] [All speakers(xxxxxx):32020] Failed to connect to service Google-Cast-Group-6aed0016802f4e44b11f0b286843e393._googlecast._tcp.local., retrying in 5.0s

2021-02-06 02:53:40 WARNING (zeroconf-ServiceBrowser__googlecast._tcp.local._298) [homeassistant.components.cast.discovery] setup_internal_discovery failed to get info for 6aed0016-802f-4e44-b11f-0b286843e393, Google-Cast-Group-6aed0016802f4e44b11f0b286843e393._googlecast._tcp.local.

jds · February 6, 2021, 5:04pm

I had the same problem, and it was a problematic docker container that would not start. Once I got rid of it, then everything started fine. I did not really need that container (addon) so I did not try reinstalling the addon.

jds · February 6, 2021, 5:08pm

I have a new strange problem with this version. Everything was running fine for a couple of days, but today I wanted to move my RPi4 (HassOS, boots from SSD, wired to ethernet) to a new spot. I discovered that after I rebooted the OS, it would not start HA again. This is repeatable: I can ping it, but cannot SSH into it and no web interface. HOWEVER, this is the odd part, if I boot it with a monitor attached, it gets to a login screen. If I just type root, it gives me the HA prompt, and completes starting up just fine. Has anyone seen this before? I wonder if it really has anything to do with this version, but could not find anything mentioned anywhere because of poor google-fu.

EDIT: After this issue, I decided I should make a backup, because I just added some new nodes to my Zwave. I saw that HA had started making a backup immediately after booting up. Did I maybe interrupt a back when I shutdown the OS? Could this cause the problem?

EDIT2: Yup, that was it. After it finished creating and uploading the snapshot, I could reboot fine.

davisstewart · February 6, 2021, 6:01pm

How do I get rid of the docker container

jds · February 6, 2021, 7:56pm

I have portainer installed, and it showed me the that the Bitwarden container was stopped. I then just uninstalled that addon and rebooted. So, if this is also your problem, you need to find which one is the problem. From SSH (if you don’t have portainer), you could use docker ps and docker ps -a to see which containers are running (the former) and all of the installed containers (the latter).

davisstewart · February 6, 2021, 8:34pm

Thanks for your response jds.

I’m not familiar with Portainer and how to use it. I think it is showing me that there is 1 red item but I cant find what it is .

2021-02-06_20h31_50

When I click, it seems to say everything is ok.

jds · February 6, 2021, 8:49pm

The top image says that you have 18 containers, one of which is not running. But then, I am guessing that the lower image is what you get when you click on that image, which shows no containers. That is odd. Try clicking on the container to see what containers you have. It could be that the stopped one is the problem. On the other hand, it could be a container that doesn’t normally run on startup, like “core-check-config”, in my case. In that case, you have some different problem.

davisstewart · February 6, 2021, 9:03pm

Exactly as you describe.

When I click it says I have no containers.

This is the image when I click on the containers.

I’m wondering does it have anything to do with this tab in Settings.

petro · February 6, 2021, 9:13pm

If it’s the hass portainer addon, you need to turn in the ability to see hidden containers

davisstewart · February 6, 2021, 9:14pm

Can you tell me how?

petro · February 6, 2021, 9:14pm

It’s a setting in the addon, not portainer

petro · February 6, 2021, 9:16pm

davisstewart · February 6, 2021, 9:17pm

Thanks got it.

Unfortunately I dont think it helps as the only one not running is the core_check_config.

Will do a reboot and see what ones do not start up.

jds · February 6, 2021, 9:33pm

Yeah, make sure it is not just restarting HA. Go to Supervisor->System->Reboot Core

davisstewart · February 6, 2021, 9:51pm

Wont let me reboot core. Get the following error, [supervisor.utils] Can’t execute restart while a task is in progress

Rebooted the host and checked Portainer.

All are running except the core_check_config.

davill · February 11, 2021, 1:31am

I have exactly the same problem as davisstewart. I upgraded to 2021.2.1 and it would not fully reboot. I get the popup message at the bottom left: “Home Assistant is starting, not everything will be available until it is finished.” It never finishes. I cannot make snapshots because:

21-02-09 21:53:34 WARNING (MainThread) [supervisor.jobs] 'SnapshotManager.do_snapshot_full' blocked from execution, system is not running - CoreState.STARTUP
21-02-09 21:54:29 ERROR (MainThread) [supervisor.utils] Can't execute wrapper while a task is in progress

Also same log warning as davisstewart regarding [homeassistant.components.recorder]. So the core is not fully started, but I don’t know why?

Core 2021.2.1, Supervisor 2021.02.6, host OS 5.11. Standard Raspberry Pi 4b.