point-4ward
commented
4 years ago ... And weirdly its all just started working again :man_shrugging:
False alarm apparently.
Closed point-4ward closed 4 years ago
point-4ward
commented
4 years ago ... And weirdly its all just started working again :man_shrugging:
False alarm apparently.
point-4ward
commented
4 years ago Reopening as there's quite a few people on the forums with the same issue so it needs investigating :slightly_smiling_face:
antro31
commented
4 years ago Looks like any request to supervisor fail.
eg: ha supervisor info returns
Get http://supervisor/supervisor/info: dial tcp 172.30.32.2:80: connect: connection refused
akandor
commented
4 years ago supervisor and core command on cli gives back
... connect: connection refused
108085
commented
4 years ago After i restarted (pulled the plug) everything was fine again. (Hass.io on RPi 3B)
blackskull182
commented
4 years ago HA 0.108.9 running on Hassos Rpi 3b+: Same issue here.
Nothing updated by myself. Also presume it updated to 221 through the night.
Tried to reboot, no way to make it work again.... :(
antro31
commented
4 years ago Hard reboot (unplugging my RPI3b+) solved the issue for me. Just realized that there is a supervisor 222 now available. Does it solve this issue? (Not stated in the release notes).
AndyRPH
commented
4 years ago Having the same issue, full reboot did not help. Can this be fixed from mounting the SD card on another computer?
josephkiser04
commented
4 years ago Same issue here today. Installed nothing new. Current install is on a VM. Any idea what is causing this?
Rayman44
commented
4 years ago same on my Rpi4. also when i try to open deconz.
| arch | armv7l |
|---|---|
| dev | false |
| docker | true |
| hassio | true |
| os_name | Linux |
| os_version | 4.19.114-v7l |
| python_version | 3.7.7 |
| timezone | Europe/Stockholm |
| version | 0.109.6 |
| virtualenv | false |
Logginformation (ERROR) Logger: homeassistant.components.hassio.http Source: components/hassio/http.py:105 Integration: Hass.io (documentation, issues) First occurred: 14:09:00 (20 occurrences) Last logged: 14:45:12
Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
Rayman44
commented
4 years ago Restart and reboot...
Client error on /homeassistant/info request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)] Client error on /homeassistant/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)] Client error on /host/reboot request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
Rayman44
commented
4 years ago Power reboot sloved the issue for now
liudger
commented
4 years ago Got the same issue on odroid N2. I’ll try a hard reboot
2020-06-03 16:44:21 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
LaStrada
commented
4 years ago Happend to me yesterday running 0.110.4 on my RPI4. After rebooting I can't connect to ssh (root / ssh addon) or access HA in the browser.
Error response from daemon: Container cfee843e2af143dd0b56ea855a65fb378adaad6869ffdb9582cfcde75c8d5e70 is not running Connection to 10.0.0.4 closed.
Had a lot of warnings like the one @liudger and @Rayman44 are showing above here before I rebooted.
drthanwho
commented
4 years ago I get this every so often too. It's so frustrating because you loose access to any mingfull way of restarting. Usually I get it happening after I restart HA but I got it a few minutes ago but this time from trying to access an add-ons url page.
The only way I ever mananged to get it back is always from pullling the plug :cry:
Running on an Rpi3b+ and these are the logs
2020-06-04 23:22:05 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /info request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-06-04 23:22:05 WARNING (MainThread) [homeassistant.components.hassio] Can't read last version:
2020-06-04 23:22:12 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]Not sure if relevant but before these logs I got the following 150 times....
2020-06-04 23:21:26 WARNING (MainThread) [asyncio] socket.send() raised exception.
liudger
commented
4 years ago It's indeed more often now. Everyday is not a good sign :(
it started with this error this time:
2020-06-04 06:50:50 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection.281473008300176] Disconnected: Did not receive auth message within 10 seconds
drthanwho
commented
4 years ago The biggest problem from looking at this on different issues is that it seems to happen for different reasons to different people. Although I could be wrong
But almsot everyone gets something like this Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)] so perhaps they could find a way to do something about it when this error gets logged. Like force HA to reboot which seems to be the only way of getitng out of it.
balloob
commented
4 years ago When that error happens, it means that Home Assistant is unable to talk to the supervisor. The supervisor is also the one serving the panel so that is all makes sense. Why the supervisor is down? 🤷
drthanwho
commented
4 years ago The problem then is (at lease if you're running Supervised) there is absolutely no way of restating and all you can do is unplug the power. I also would have assumed that when this happens during a restart of HA that safe mode would kick in but it doesn't.
What would be potential reasons for the supervisor to be down? And how does it go down if it happens not during a reboot? :shrug:
drthanwho
commented
4 years ago Also @pvizeli is it possible that this issue happens because of the supervisor updates? Do the updates try to install themselves or do they only install if we do it? I remember last time I got this issue was from restarting while doing an edit in yaml and then supervisor went down and after unpluging power to do a power cycle, then superivsor was back but also updated itself.
Now I just saw there was a new HassOS update released just yesterday so wonder if HA attempted to update the OS itself and ended up causing this as well.
liudger
commented
4 years ago I have the same feeling that the supervisor update is causing this issue
DickiePhitt
commented
4 years ago Like others, suddenly lost access to Supervisor, Files & Reboot. Lovelace OK. Stupidly tried a hard reset but no amount power ups is making HA restore. I'm hobby user, not a coding expert, so have no idea how to restore system. It needs resolving, with clear instructions how to get system back up and running.
aliilhami
commented
4 years ago Using a Rpi4 and having this issue since last 1 month from v109. Now upgraded to v0.111.4 and started to having same issue on every 2 days!! Power cycle does not help, it doesn't come up after a power cycle. I have to do a full recover. And after recovery it is happening again and again. It's practically impossible to use the device anymore. Please fix this ASAP!
axilleas
commented
4 years ago I just faced the same issue today, after almost 3 years running HA-supervised. The relevant errors logs from docker logs -f hassio_supervisor:
20-06-29 20:50:30 ERROR (MainThread) [supervisor.api.security] Invalid token for access /homeassistant/options
20-06-29 20:50:30 ERROR (MainThread) [supervisor.api.security] Invalid token for access /supervisor/options
20-06-29 20:50:30 ERROR (MainThread) [supervisor.api.security] Invalid token for access /info
20-06-29 20:50:30 ERROR (MainThread) [supervisor.api.security] Invalid token for access /ingress/panels
20-06-29 20:51:25 ERROR (MainThread) [supervisor.api.security] Invalid token for access /discovery
20-06-29 20:53:08 ERROR (MainThread) [supervisor.api.security] Invalid token for access /app/entrypoint.jsRpi4, with an external SSD as the root filesystem, running ArchLinuxARM and HA-supervised. I switched to the external SSD just yesterday, not sure it has something to do with it.
I ended up removing the containers/images and re-installing HA supervised. It now works again. I haven't tested rebooting yet :crossed_fingers:
Midnitte
commented
4 years ago Looks like I am also getting this issue when trying to access things like the supervisor or addons (glances, file editor, etc). I only noticed as I was going to upgrade to 0.112...
The only relevant log I see is:
Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
Running on a RPI3B with an SD card.
| arch | armv7l |
|---|---|
| chassis | embedded |
| dev | false |
| docker | true |
| docker_version | 19.03.5 |
| hassio | true |
| host_os | HassOS 3.13 |
| installation_type | Home Assistant |
| os_name | Linux |
| os_version | 4.19.114-v7 |
| python_version | 3.7.7 |
| supervisor | 227 |
| timezone | America/New_York |
| version | 0.111.0 |
| virtualenv | false |
drthanwho
commented
4 years ago Just happened again after months. Although most times in the past it has been during updating HassOS or Operating System updates. This time it happened just after I was updating some HACS components and then went to restart HA as they were requiring a restart after the update. Apart from that it is exactly the same issue. No way to restart apart from pulling the plug
2020-07-18 14:39:03 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-18 14:46:15 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-18 14:47:22 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-18 14:47:32 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-18 14:50:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /info request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-18 14:50:36 WARNING (MainThread) [homeassistant.components.hassio] Can't read last version: 
sebstr1
commented
4 years ago Ive been running ha for a long time on rpi4 from an ssd. This happend to me aswell a few months back. I remember that it occured after an update..
Log:
Client error on api app/entrypoint.js request Cannot connect to host 172.30.XX.X:80 ssl:None [Connect call failed ('172.30.XX.X', 80)]
MarkFiroozfar
commented
4 years ago Adding another data point... Very long time Hassio install on rpi3, first time occurrence of this error. Can access files via SAMBA share, but unable to initiate a reboot of supervisor. At this point, due to the various reports of rendering the unit inoperable, I am avoiding a hard power cycle reset.
Has there been a workaround or solution posted?
Log Details (ERROR)
Logger: homeassistant.components.hassio.http
Source: components/hassio/http.py:105
Integration: Hass.io (documentation, issues)
First occurred: 11:18:14 AM (1 occurrences)
Last logged: 11:18:14 AM
Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]Pulled from log file:
2020-07-21 09:58:33 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/info request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-21 09:58:33 WARNING (MainThread) [homeassistant.components.hassio] Can't read last version:
2020-07-21 10:53:34 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/info request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-21 10:53:34 WARNING (MainThread) [homeassistant.components.hassio] Can't read last version:
2020-07-21 11:09:49 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-21 11:09:56 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-21 11:10:05 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-21 11:12:48 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-21 11:14:57 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-21 11:15:45 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/restart request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]
2020-07-21 11:18:14 ERROR (MainThread) [homeassistant.components.hassio.http] Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]Looks like I am also getting this issue when trying to access things like the supervisor or addons (glances, file editor, etc). I only noticed as I was going to upgrade to 0.112...
The only relevant log I see is:
Client error on api app/entrypoint.js request Cannot connect to host 172.30.32.2:80 ssl:None [Connect call failed ('172.30.32.2', 80)]Running on a RPI3B with an SD card.
arch armv7l chassis embedded dev false docker true docker_version 19.03.5 hassio true host_os HassOS 3.13 installation_type Home Assistant os_name Linux os_version 4.19.114-v7 python_version 3.7.7 supervisor 227 timezone America/New_York version 0.111.0 virtualenv false
Just to follow up on my situation, I had an inadvertent power outage and once it rebooted everything seemed fine and I was able to upgrade the supervisor and system.
drthanwho
commented
4 years ago From my experience (had this happened at least 5 time in the past 6 - 7 months) the only possible work around is to power cycle your device.
However, until the issue is resolved I think the only other possible workaround would be to install HA Supervised instead where you would be able to reboot since you'd have access to the OS
mimik13
commented
4 years ago Ran into the same issue on my Pi 3. Power cycling seems to have fixed the issue temporarily.
robbinjanssen
commented
4 years ago Same here, logs are same as above. Fortunately I can connect to the host and do a reboot.
What can we do to provide more debugging info? :) Maybe find common factors?
Addons I use:
sparcopt
commented
4 years ago Just got the same error on a HA rpi4 installation with <1 month with very few add-ons.
sebstr1
commented
4 years ago Do you have HACS installed?
On Wed, Aug 12, 2020, 16:09 sparcopt notifications@github.com wrote:
Just got the same error on a HA rpi4 installation with <1 month with very few add-ons.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/home-assistant/supervisor/issues/1707#issuecomment-672893694, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADRJLP5ALBYVNRPJL2TGAPDSAKPAVANCNFSM4M35QQQA .
KentuckyMC
commented
4 years ago I believe this issue is the same issue as #1576 . Maybe an idea to merge those 2 together?
I wasn't able to get to the supervisor screens as well. I've now hard reboot (power plug) the RBPi4 and it works again. Before it, in my settings the supervisor version showed me: 229 (in settings > info). Now after the hard reboot it shows me 231. So it really looks like something is going wrong over there, that it is forced to update or something and break stuff. for @robbinjanssen , my list of addons:
sparcopt
commented
4 years ago Do you have HACS installed?
Yes I have it.
Like others mentioned, I did a hard reboot (power plug) and it works again. I can also add that my rpi4 (including sd card) are brand new.
mkjustuk
commented
4 years ago The same issue for me started today, shutdown an power-up solved it.
Debian 10, HA Supervised in a docker container running on an i7 Sandy Bridge
The issue is definitely Supervisor updating. In info before reboot - 229, just after, 231
I have the following addons; File Editor Node-Red Samba Visual Studio Code Mosquitto MQTT Google drive backup
HACS is also installed.
I see now that core wants to upgrade - could that be related?
sebstr1
commented
4 years ago Starting to think its related to HACS.. Might be a longshot tho
ximon
commented
4 years ago I've just had this issue, temporarily solved with a reboot. I dont have HACS installed.
It has been running faltlessly for months, migrated from Pi 3b+ to Pi 4 and within one week this happened.
Raspberry Pi 4 4GB New 32GB SD Card Home Assistant Core 0.113.3 OS 4.11 Supervisor 231
KentuckyMC
commented
4 years ago Hmm, the last one is without HACS. @ximon do you have any other add-ons?
KentuckyMC
commented
4 years ago The same issue for me started today, shutdown an power-up solved it.
Debian 10, HA Supervised in a docker container running on an i7 Sandy Bridge
The issue is definitely Supervisor updating. In info before reboot - 229, just after, 231
I have the following addons; File Editor Node-Red Samba Visual Studio Code Mosquitto MQTT Google drive backup
HACS is also installed.
I see now that core wants to upgrade - could that be related?
I don't think it's the core that's causing the issue. I believe that update was a bit later then these issues started. I've upgraded the core without problem already. It seems like a real supervisor issue (in combination with something).
ximon
commented
4 years ago Hmm, the last one is without HACS. @ximon do you have any other add-ons?
At the time I had the following installed:
I installed Haas.io Google drive backup and Portainer just in the past week, the rest have been installed for several months now.
KentuckyMC
commented
4 years ago Things like the Node Red, File editor and Samba share are commonly used as well. My addons are running for several months as well without issues untill that last supervisor update (looks like).
aliilhami
commented
4 years ago We can filter out Node Red, as it happened to me on previous versions of supervisor without node red installed. I have HACS, file editor, samba share, duck dns, ftp, google drive backup addons installed.
This happened to me one month earlier and kept happening 3 times every time when I recovered from backup. I reinstalled from zero and only recovered addons not system files and changed sdcard, now problem seems resolved. Since I'vr changed so many items at once, I cannot say which one resolved my problem.
gralin
commented
4 years ago Happened to me today to, after upgrading to latest HASSIO and HA. I am using following addons:
I also use HACS.
freman
commented
4 years ago I think I'm suffering from this too, was working fine like 3 days ago, I noticed that node red automations weren't working last night, poke around get the Unable to load the panel source: /api/hassio/app/entrypoint.js error on the frontend
ssh in and the supervisor is rebooting over and over again
20-08-17 02:49:59 INFO (MainThread) [__main__] Initialize Supervisor setup
20-08-17 02:50:00 INFO (MainThread) [supervisor.bootstrap] Initialize Supervisor Sentry
20-08-17 02:50:00 INFO (MainThread) [supervisor.bootstrap] Setup coresys for machine: raspberrypi3
20-08-17 02:50:00 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attach to Supervisor homeassistant/armv7-hassio-supervisor with version 234
20-08-17 02:50:00 INFO (MainThread) [__main__] Setup Supervisor
20-08-17 02:50:00 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
20-08-17 02:50:01 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
20-08-17 02:50:01 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: de.pengutronix.rauc - /
20-08-17 02:50:01 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.NetworkManager - /org/freedesktop/NetworkManager/DnsManager
20-08-17 02:50:01 INFO (MainThread) [supervisor.host.info] Update local host information
20-08-17 02:50:01 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-08-17 02:50:01 INFO (MainThread) [supervisor.host.services] Update service information
20-08-17 02:50:01 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-08-17 02:50:01 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-08-17 02:50:01 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-08-17 02:50:01 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-08-17 02:50:01 INFO (MainThread) [supervisor.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
20-08-17 02:50:01 INFO (MainThread) [supervisor.host.services] Reload local service hassos-apparmor.service
20-08-17 02:50:01 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
20-08-17 02:50:01 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/armhf-hassio-dns with version 9
20-08-17 02:50:01 INFO (MainThread) [supervisor.misc.forwarder] Start DNS port forwarding to 172.30.32.3
20-08-17 02:50:01 INFO (MainThread) [supervisor.plugins.dns] Restart CoreDNS plugin
20-08-17 02:50:01 INFO (SyncWorker_0) [supervisor.docker.interface] Restart homeassistant/armhf-hassio-dns
20-08-17 02:50:08 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
20-08-17 02:50:08 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/armv7-hassio-audio with version 17
20-08-17 02:50:08 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/armhf-hassio-cli with version 25
20-08-17 02:50:08 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/armhf-hassio-multicast with version 2
20-08-17 02:50:08 INFO (MainThread) [supervisor.plugins.multicast] Restart Multicast plugin
20-08-17 02:50:08 INFO (SyncWorker_0) [supervisor.docker.interface] Restart homeassistant/armhf-hassio-multicast
20-08-17 02:50:15 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-08-17 02:50:15 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/raspberrypi3-homeassistant with version 0.113.0
20-08-17 02:50:15 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /
20-08-17 02:50:15 INFO (MainThread) [supervisor.hassos] Detect HassOS 4.11 / BootSlot A
20-08-17 02:50:16 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/a0d7b954 repository
20-08-17 02:50:16 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/core repository
20-08-17 02:50:16 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/7ad98f9c repository
20-08-17 02:50:16 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/62c7908d repository
20-08-17 02:50:16 INFO (MainThread) [supervisor.store] Load add-ons from store: 79 all - 79 new - 0 remove
20-08-17 02:50:16 INFO (MainThread) [supervisor.addons] Found 10 installed add-ons
20-08-17 02:50:16 INFO (SyncWorker_3) [supervisor.docker.interface] Attach to 62c7908d/armv7-addon-autobackup with version 1.0.2
20-08-17 02:50:16 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to hassioaddons/log-viewer-armv7 with version 0.8.0
20-08-17 02:50:16 INFO (SyncWorker_2) [supervisor.docker.interface] Attach to dwelch2101/zigbee2mqtt-edge-armhf with version test
20-08-17 02:50:16 INFO (SyncWorker_5) [supervisor.docker.interface] Attach to hassioaddons/zwave2mqtt-armv7 with version 0.6.0
20-08-17 02:50:16 INFO (SyncWorker_6) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-ssh with version 8.6.0
20-08-17 02:50:16 INFO (SyncWorker_1) [supervisor.docker.interface] Attach to hassioaddons/sonweb-armv7 with version 0.11.0
20-08-17 02:50:16 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-configurator with version 5.0.0
20-08-17 02:50:16 INFO (SyncWorker_4) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-check_config with version 3.4.0
20-08-17 02:50:16 INFO (SyncWorker_7) [supervisor.docker.interface] Attach to hassioaddons/node-red-armv7 with version 6.1.4
20-08-17 02:50:16 INFO (SyncWorker_3) [supervisor.docker.interface] Attach to hassioaddons/mqtt with version 1.2.0
20-08-17 02:50:16 INFO (MainThread) [supervisor.snapshots] Found 7 snapshot files
20-08-17 02:50:17 INFO (MainThread) [supervisor.discovery] Load 0 messages
20-08-17 02:50:17 INFO (MainThread) [supervisor.ingress] Load 0 ingress session
20-08-17 02:50:17 INFO (MainThread) [supervisor.misc.secrets] Load Home Assistant secrets: 0
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/docker/api/client.py", line 261, in _raise_for_status
response.raise_for_status()
File "/usr/local/lib/python3.8/site-packages/requests/models.py", line 941, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.40/images/sha256:57944ca7e03c02cc013475dd4200222d939caeeefeb9faa7a6f7d1b6957e52a0/json
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/local/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/usr/src/supervisor/supervisor/__main__.py", line 47, in <module>
loop.run_until_complete(coresys.core.setup())
File "uvloop/loop.pyx", line 1456, in uvloop.loop.Loop.run_until_complete
File "/usr/src/supervisor/supervisor/core.py", line 148, in setup
if await self.sys_run_in_executor(self.sys_docker.check_denylist_images):
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/supervisor/supervisor/docker/__init__.py", line 239, in check_denylist_images
for image in self.images.list():
File "/usr/local/lib/python3.8/site-packages/docker/models/images.py", line 364, in list
return [self.get(r["Id"]) for r in resp]
File "/usr/local/lib/python3.8/site-packages/docker/models/images.py", line 364, in <listcomp>
return [self.get(r["Id"]) for r in resp]
File "/usr/local/lib/python3.8/site-packages/docker/models/images.py", line 316, in get
return self.prepare_model(self.client.api.inspect_image(name))
File "/usr/local/lib/python3.8/site-packages/docker/utils/decorators.py", line 19, in wrapped
return f(self, resource_id, *args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/docker/api/image.py", line 245, in inspect_image
return self._result(
File "/usr/local/lib/python3.8/site-packages/docker/api/client.py", line 267, in _result
self._raise_for_status(response)
File "/usr/local/lib/python3.8/site-packages/docker/api/client.py", line 263, in _raise_for_status
raise create_api_error_from_http_exception(e)
File "/usr/local/lib/python3.8/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
raise cls(e, response=response, explanation=explanation)
docker.errors.APIError: 500 Server Error: Internal Server Error ("readlink /mnt/data/docker/overlay2: invalid argument")I was able to resolve by sshing in and running
mv /mnt/data/docker /mnt/data/dockerred
rebootit re-installed everything, still have some plugin quirks to solve (cos they didn't auto-reinstall and enable) but at least hass is running again
KentuckyMC
commented
4 years ago Ok got a new update here again. I saw the supervisor update today to 235, clicked on update and after refresh I saw the home assistant page again. And guess it, same error with the entrypoint.js (on file editor, node-red etc.). When I look into the settings it still say 234 version. I guess when I'm home again and unpower my RPi, it'll will say version 235.
There is really something wrong with the updates from the supervisor, don't know what it is, if I can help someone with logs or something, please ask it. Very annoying that when updating Supervisor the system needs a hard reset.
UPDATE: After hard reboot everything works again.
jiangnan1710
commented
4 years ago I think maybe I have found some method to solve this problem. You should check the container hassio_supervisor's IP address. It may changed to another but I don't know why.
ludeeus
commented
4 years ago Duplicate of #1576
yschroeder
commented
4 years ago Same problem (HassOS, RPi4). Reboot solved the issue.
Home Assistant release with the issue: 109.4
Operating environment (HassOS/Generic): Proxmox > Debian VM > Docker > HA supervised
Description of problem:
Cannot access supervisor as of this morning, presume it updated to 221 through the night? Trying to open supervisor (or any addon webui) gives the message "Unable to load the panel source: /api/hassio/app/entrypoint.js."
Also seems to prevent restarting homeassistant from the server controls page.
Have tried rebooting the machine. Reboots fine but issues persist.
Supervisor logs: Looks normal tbh,,,