-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supervisor integration fails to load #90558
Comments
Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) hassio documentation |
Also having this issue - happy to provide logs if required. Updates do not show anymore, and add-ons either. Once a fix is out, is there a way to force updates through CLI since the GUI for supervisor/updates no longer works for those with this error? |
I also have the same issue. Settings > Add-Ons view does not open either. Get this in the logs: Full logs show this error: |
Same issue here. I've revered the core back a few versions and it still fails the same way. I'm not sure what is going on but it somehow preventing my frigate notifications from working correctly too |
I get the same issue, it have try many ways, but it does not work, so i guess may be it's not our problem, maybe it's to do with the server |
To add: am having the exact same issue. The "addons" page is also not willing to load. Inside the logs of the Supervisor container I do find some hints that doubletake is causing issues (but cannot determine if this is also the reason why the supervisor is causing issues). Relevant logs:
|
I have the same issue. In Addition the back-up List is Not loading, so no way to roll back. |
I suspect everyone won't be able to do what I did to work around this. I was running an unsupported installation so I spun up a debian 11 wm and installed the supervised hassio and then copied all my files from the previous vm to this one and brought everything back online. Most things seem to work and the issue I had is gone. Not really a solution but it's something if you have the ability |
Is there a way to download the files from GitHub? My mini pc isn’t powerful enough to spin up a new VM. |
Had same issue and doing a rebuild worked for me. I have HASS OS in a VM and I simply entered ´ha core rebuild´ and it worked for me. All missing addons funcitnality and hacs repositories appeared after that. Good luck! |
Did not work for me unfortunately. Is there a way to roll back using ha core ? |
Same problem |
Same, Add-Ons page and the same error as everyone else. |
I'm also experiencing the exact same issues. Maybe it's finally time for me to start running Home Assistant in a supported configuration (not LXC container). |
How to fix this, I'm running hass supervised. I guess I have to edit this in the docker container? Which one? |
find the os.py file via SSH |
Indeed, edit the file within the docker container: |
I connected to the hassio_supervisor container console via Portainer, |
That was it, thank you! Back up and running! |
how do I fix it in this installation? On my installation : /usr/share/hassio/homeassistant |
Ah. Okay so there are two supervisor/hassio issues currently going on in mass scale. One is hassio failing to load (therefore also add-ons interface and a few other features) and one is supervisor itself. The first one seems to be bad code/bad handling of waiting for processes, the second one unfortunately is due to an install problem. Either caused by the user or home assistant itself during an update. Yours is the second Which install method are you using? Usually the second can be 'solved' (at least until another update) but reinstalling and not restoring home assistant core itself. |
I use a Home Assistant Supervised installation. |
Perfect. Even easier. Make sure cgroup and apparmor are applied correctly (adding to cmdline if needed) and just rerun the supervised installation script. All your data will stay but make a backup just in case. Does that fix anything? |
Oh, I'm very happy that you want to help me, but I'm very sorry, but I can't do anything with these terms. I am not familiar with them. |
The issue got fixed in Home Assistant Release 2024.4 for me. |
Glad to know. Just be careful because this specific issue appears after a bad install it seems. So the next update might bring it back if they didn't actually address the root issue. The solution to this was always re applying home assistant. |
I used a new installation of 2023.4, and I still have this problem. kvm version haos.
|
It seems that this has something to do with the inability to access certain URLs, which in the case of China is that if you can't access certain servers, this can't be initialized. |
So to review, if I have installed HomeAssistant via the Raspberry Pi image, which does not have inbuilt SSH access, I cannot fix this issue. I've got |
unsure if this is the correct thread for this... I am seeing issues with supervisor not loading/set up on reboot of server |
more info... (when hovering the "Failed to set up" )
|
gesh... sucks this still has nobody assigned to it. |
Hi. Same problem here:
Home Assistant 2023.8.4 |
Same here, no way to fix with backups, and i can't find os.py file. |
Hi everyone! The method described above still working. I have solved my issue. |
Same problem here... running HAOS in a VM - after a reboot the error occures... Logger: homeassistant.config_entries Error setting up entry Supervisor for hassio Home Assistant 2023.8.4 |
Same here: Logger: homeassistant.config_entries Error setting up entry Supervisor for hassio Home Assistant 2023.9.0 Even restoring backup from 2013.8.4 didn't work. |
My supervisor started working again.
|
I'm having this exact same issue with 2023.9.2 This is a brand new install on a brand new Hyper-V machine using the stock-supplied VHDX Logger: homeassistant.config_entries
Source: components/hassio/handler.py:540
First occurred: 5:48:56 PM (1 occurrences)
Last logged: 5:48:56 PM
Error setting up entry Supervisor for hassio
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 668, in async_setup_entry
await coordinator.async_config_entry_first_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 257, in async_config_entry_first_refresh
await self._async_refresh(
File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 977, in _async_refresh
await self.hassio.refresh_updates()
File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 37, in _wrapper
data = await funct(*argv, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 540, in send_command
request = await self.websession.request(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 560, in _request
await resp.start(conn)
File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 899, in start
message, payload = await protocol.read() # type: ignore[union-attr]
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 616, in read
await self._waiter
asyncio.exceptions.CancelledError: Global task timeout Any suggestions on how to proceed? |
For anyone who has this problem and you are running pihole, please try to bypass the pihole DNS and try as mentioned here: #99862. Props to https://github.com/SalvatoreITA for the solution! |
I have PiHole in my network. Manually setting DNS to 1.1.1.1 in HomeAssitant network settings and restarting it fixes the problem. Thanx! |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The problem
Both on 2023.4.0b0 and 0b2
What version of Home Assistant Core has the issue?
Home Assistant 2023.4.0b2
What was the last working version of Home Assistant Core?
Home Assistant 2023.3.1
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Supervisor
Link to integration documentation on our website
https://www.home-assistant.io/integrations/hassio/
Diagnostics information
home-assistant_2023-03-31T03-41-45.513Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: