Hey
Does anyone know what they latest version of supervisor wont start in my case?
Does anyone know how I restore if I can get to the restore/backup menu?
Here is my log
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/udev.sh
[15:23:33] INFO: Setup udev backend inside container
[15:23:33] INFO: Update udev information
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
s6-rc: info: service legacy-services successfully started
[15:23:33] INFO: Starting local supervisor watchdog...
22-07-06 15:23:36 INFO (MainThread) [supervisor.bootstrap] Use the old homeassistant repository for machine extraction
22-07-06 15:23:36 INFO (MainThread) [__main__] Initializing Supervisor setup
Traceback (most recent call last):
File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/usr/src/supervisor/supervisor/__main__.py", line 41, in
coresys = loop.run_until_complete(bootstrap.initialize_coresys())
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
return future.result()
File "/usr/src/supervisor/supervisor/bootstrap.py", line 63, in initialize_coresys
coresys = CoreSys()
File "/usr/src/supervisor/supervisor/coresys.py", line 66, in __init__
self._docker: DockerAPI = DockerAPI()
File "/usr/src/supervisor/supervisor/docker/__init__.py", line 106, in __init__
self._info: DockerInfo = DockerInfo.new(self.docker.info())
File "/usr/src/supervisor/supervisor/docker/__init__.py", line 62, in new
data["CgroupVersion"],
KeyError: 'CgroupVersion'
22-07-06 15:23:36 ERROR (MainThread) [asyncio] Unclosed client session
client_session:
[15:23:36] WARNING: Halt Supervisor
s6-rc: info: service legacy-services: stopping
[15:23:36] INFO: Supervisor restart after closing
[15:23:36] INFO: Watchdog restart after closing
s6-svwait: fatal: supervisor died
[15:23:36] INFO: Supervisor restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info:
I got mine to start finally, but there have been a lot of issues.
First I have gotten a lot of restarts due to errors with max pending websocket requests, which is probably what you see now.
I am now up and running, but the system is now marked as unsupported and when I looked through the logs I found a line checking the site starting with https://version, but the update should have changed that to https://checkonline, so I am not even certain I am on the new supervisor version anymore.
Experienced the same issue today, I restored last backup and it fixed the issue
I have HA on a virtual machine on Proxmox, so for me it has been “quite easy” to restore a backup accessing the console.
Well from the console using the command: ha backups
you get the list of backups present on your machine (hoping you did a recent backup…), find the one just before the upgrade. and take note of the slug (i.e. something like slug: bf824b61)
execute the restore using: ha backups restore <thenumberofslug>
sit and wait…
after the restore, I had full access to my ha
docker container ls -a shows that the supervisor has got recently updated, about 1 hour ago, I did not trigger the update, and now the system is broken, anyone knows how to restore a previous version of the docker image that works, and prevent auto update? I do not remember updating supervisor manually, so it must have been done automatically.
Ah that makes sense then. Was wondering how I hadn’t seen this.
Ubuntu isn’t supported as the host OS of a supervised install. There are many things different about it from vanilla debian and there is no testing done on it to identify differences prior to release. Looks like you found a new one.
I would suggest using a supported installation method.
