I was about to show someone my Grafana graphs in HA when I started getting the ‘Unable to load the panel source: /api/hassio/app/entrypoint.js’ error. In researching, this appears to be related to hassio-supervisor not running. I am able to SSH into my HA server and supervisor is not running. A restart will show it trying for 5 seconds over and over again until I stop it. I rebooted the whole server and none of my containers were started, presumably because supervisor can’t start. I was able to manually start a number of containers since I had the list of names in my SSH buffer.
I am seeing the following error in the logs:
20-03-03 17:23:58 INFO (MainThread) [__main__] Initialize Supervisor setup
Traceback (most recent call last):
File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/src/supervisor/supervisor/__main__.py", line 41, in <module>
coresys = loop.run_until_complete(bootstrap.initialize_coresys())
File "uvloop/loop.pyx", line 1456, in uvloop.loop.Loop.run_until_complete
File "/usr/src/supervisor/supervisor/bootstrap.py", line 61, in initialize_coresys
coresys.hwmonitor = HwMonitor(coresys)
File "/usr/src/supervisor/supervisor/hwmon.py", line 22, in __init__
self.monitor = pyudev.Monitor.from_netlink(self.context)
File "/usr/local/lib/python3.7/site-packages/pyudev/monitor.py", line 121, in from_netlink
raise EnvironmentError('Could not create udev monitor')
OSError: Could not create udev monitor
20-03-03 17:23:58 ERROR (MainThread) [asyncio] Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7fe93974d410>
20-03-03 17:23:58 ERROR (MainThread) [asyncio] Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7fe939778e10>
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Additionally, I cannot resolve anything on that box. The /etc/resolv.conf file is empty and is linked to a ‘…/run/…’ location. I assume that since supervisor is not running, that runtime location doesn’t exist.
It also appears that the age of the supervisor container is < 4 hours so did it do an auto update?
Apologies to @frenck as I did the docker pull before reading his comment about not doing that (in the above referenced github ticket). I am working again now that I did the install. I did use the docker pull commands but not sure what actually caused it to start working, whether it was the install script or the docker pull. I also had an issue with DNS resolution that I had to fix before the box could resolve the update URLs.
Same issue for me. Had some issues with the suggested fix. Ran both suggestions from @night. To run the curl command I originally ran it with ‘sudo’ but that didn’t work. Got an error ’ bash: line 133: /etc/hassio.json: Permission denied’ had to login as root and then run it. That worked and I’m back up and running. But, not sure whether it was just the curl command or the curl command and the docker commands were required to resolve the issue.
Same issue here on ubuntu 18.04 since this morning.
Yesterday, HA showed the supervisor update in the Supervisor section, but I did NOT install it.
Apparently, it did not stop it from being installed automatically a couple of hours later…
This is not the first time these automatic updates broke stuff. The last time was the introduction of the DNS thing that broke internet connectivity for a lot of people.
Ugh, glad I found this thread, been pulling my hair out as to why things were suddenly having problems! The latter recommendations worked to resolve my problem. Not a fan of automatic updates, I’ve stopped unattended-upgrades in Ubuntu 18.04 because of that.