Update of Home assistant or addons failed - system not healthy

Installation Home Assistant OS
,
22

Thanks for this!

I had just installed Ouroboros, a python version of Watchtower, making updating my many containers running on my server very easy! Plus with a notification sent to my phone daily with the list of updated container.
But of course my HA supervisor didn’t like it, even though all HA related container were in the exclusion list in Ouroboros. As you said, after deleting the container and it’s image, HA was healthy and supported again.

Did you find any workaround? Auto-updating is super handy for sure…
I am thinking of a script, to:

  • Create the container - Image will be auto-downloaded if not there (Ouroboros has a “run once option”)
  • Keep it up for maybe 15-20 minutes
  • Stop the container
  • Delete the container
  • Delete the image

All this managed by CRON…

23

@mitch
That will only get you working temporarily,
Soon after you’d notice that it is back to being problematic.

@dtalens
Thank you, that approach is much easier and quicker then a full update / reboot

What I don’t get is that I had docker in Ubuntu method working for very long time and very steadily, and all of a sudden with some Supervisor upgrade this problem started happening, and on every Home Assistant Update or on every Add-on update I have to do this dance to get it working.

I get it, it is not officially supported, but as seen in this thread and many others, lots of people are using this setup.
Why intentionally break it?
If a reboot fixes it, or if a supervisor restart fixes it, it is obvious that at some point after the restart, supervisor is running some script process to check things out and declaring it to be unsupported, effectively blocking updates.
Seeing that people have no choice but to restart the system or supervisor to proceed, and are doing so, why not add a configuration option to allow ignoring this unsupported flag and proceed regardless? Put a big warning if you want to discourage people, but forcing people to find workarounds and loopholes is not the best deterrent.

I have one system, which is an Ubuntu system, it is powerful and runs many other services aside from Dockerized Home Assistant, asking us to switch to Debian where this setup has been working for a very long time is unrealistic.

I’m not asking for it to be officially supported, what I’m asking is for it not to be intentionally handicapped.

4 Likes
24

@badabing
I have exactly the same setup and issue you describe. +1

25

Absolutely, I spend hours to figure out why my system thinks it might be unhealthy instead of fixing it when it is really unhealthy.

26

GNU Debian and latest version of Docker installed two weeks ago after my Raspian install would no longer run Supervisor reliably. Supervisor would stop after 5 mins to 1 day with no error.
Today I see supervisor has no access to the internet and getting similar messages in log. Reboot, update and upgrade reboot, remove WG and DuckDNS reboot, add loopback to etc/host reboot all failed. Tried restarting Docker container for Supervisor and have a clean log file. However, after a reboot i get

19-02-14 10:12:53 WARNING (MainThread) [supervisor.updater] Can't fetch versions from https://version.home-assistant.io/stable.json: Cannot connect to host version.home-assistant.io:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1125)')]
19-02-14 10:12:53 WARNING (MainThread) [supervisor.jobs] 'Updater.fetch_data' blocked from execution, no supervisor internet connection
19-02-14 10:12:53 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 6 Home Assistant secrets
19-02-14 10:12:53 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/raspberrypi4-homeassistant with version 2021.3.4
19-02-14 10:12:53 INFO (MainThread) [supervisor.hassos] No Home Assistant Operating System found
19-02-14 10:12:54 WARNING (MainThread) [supervisor.jobs] 'StoreManager.update_repositories' blocked from execution, no supervisor internet connection
27

Your time is wrong.
It thinks the certificate is in the future so won’t connect to the server.
Set your time.

28

@dtalens, thanks!
It worked for me.

sudo docker restart hassio_supervisor

29

Yes, this solved the problem for me.

Followed the instructions to update from here: Install Docker Engine on Debian | Docker Documentation (However I did not apply uninstall)

30

I have same message for latest update (Oct.) and I’m running my HA on RASP4
Any advice?

1 Like
31

Following an advice online I did this via SSH and it solved the problem. It took a while to run…
ha su repair
ha core rebuild
ha host reboot

9 Likes
32

I have debian, rebooting doesn’t help me, although everything worked before. To date, I still can’t update
{
“home_assistant”: {
“installation_type”: “Home Assistant Supervised”,
“version”: “2022.9.6”,
“dev”: false,
“hassio”: true,
“virtualenv”: false,
“python_version”: “3.10.5”,
“docker”: true,
“arch”: “armv7l”,
“timezone”: “Europe/Moscow”,
“os_name”: “Linux”,
“os_version”: “5.10.60-v7l+”,
“supervisor”: “2022.10.0”,
“host_os”: “Raspbian GNU/Linux 10 (buster)”,
“docker_version”: “20.10.18”,
“chassis”: “”,
“run_as_root”: true
}Снимок1

Снимок2
Снимок2992×56 8.81 KB

33

I have this same configuration, and the same issue… from the moment I updated to supervisor version 2022.10.0. Tried other ideas on this page. Everything is up to date, including docker, and no other problems or errors in the configuration are noticeable.

… just figured out it was complaining (for the first time) about other containers that I run (in my case just Portainer). I removed that container and the updates are working… a bit annoying really, but ok.

1 Like
34

Thanks, works for me! Good job figuring this out!
Stopping portainer was actually enough for me to enable updates.

sudo docker stop portainer

Then refresh the Updates page in HA, until you can update something.
Then don’t forget to start portainer again:

sudo docker start portainer

You could do this as soon as the last update has been started…

2 Likes
35

This also worked for me.
I was not able to install Z-Wave JS Addon or any Addons at all.
But now it is working.
Thanks

36

Thank you! That helped!

37

Topicstarter @Freestila!
Set solved status to finded answer!
@plaksnor finded a solution.
But I preferred to remove the Portainer:

sudo docker stop portainer
sudo docker rm portainer
sudo reboot
2 Likes
38

Why is it considered ok to eliminate Portainer as an acceptable solution?
It sounds like a bug to me.

1 Like
39

No, it’s not a bug.

1 Like
40

Saw this today after being stopped from further updates since 10.1, complaining about unhealthy system. I’m glad I found it and was able to stop portainer and remove it. Performed updates to 10.5 like a charm. Next step to add back the portainer to docker. Running on a debian VM on proxmox. Thank you

41

Super!! This worked for me. Thank for your help!

1 Like