Supervisor 2023.11.6 upgrade borked, fixed but supervisor daemon no longer starting?

Hi all,

This morning I found my hassio install being very unhappy. After much debugging it turned out that the supervisor container was having trouble with the upgrade to 2023.11.6.

The supervisor container crashed constantly and checking my logs I noticed the following error:

Dec 20 08:37:14 raspberrypi systemd[1]: Starting Hass.io supervisor...
Dec 20 08:37:14 raspberrypi docker[4361]: hassio_supervisor
Dec 20 08:37:14 raspberrypi systemd[1]: Started Hass.io supervisor.
Dec 20 08:37:15 raspberrypi hassio-supervisor[4382]: Error: No such object: homeassistant/armv7-hassio-supervisor
Dec 20 08:37:15 raspberrypi systemd[1]: hassio-supervisor.service: Main process exited, code=exited, status=1/FAILURE
Dec 20 08:37:15 raspberrypi systemd[1]: hassio-supervisor.service: Failed with result 'exit-code'.

I was able to recover by deleting the old supervisor container and restarting a new supervisor by running:

docker run -d \
  --name hassio_supervisor \
  --privileged \
  -v /run/dbus:/run/dbus:ro \
  -v /run/udev:/run/udev:ro \
  -v /etc/machine-id:/etc/machine-id:ro \
  -v /usr/share/hassio:/data:rw \
  -v /run/docker.sock:/run/docker.sock:rw \
  --network hassio \
  --ip 172.30.32.2 \
  -e SUPERVISOR_SHARE=/usr/share/hassio \
  -e SUPERVISOR_NAME=hassio_supervisor \
  -e SUPERVISOR_MACHINE=raspberrypi4 \
  -e PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
  -e LANG=C.UTF-8 \
  -e S6_BEHAVIOUR_IF_STAGE2_FAILS=2 \
  -e S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0 \
  -e S6_CMD_WAIT_FOR_SERVICES=1 \
  -e S6_SERVICES_READYTIME=50 \
  -e S6_SERVICES_GRACETIME=10000 \
  -e SUPERVISOR_API=http://localhost \
  -e CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1 \
  ghcr.io/home-assistant/armv7-hassio-supervisor:2023.12.0

Hassio is somewhat happy again but the connection between the supervisor daemon and the docker container is now gone. If I start the supervisor daemon the running supervisor docker container is stopped and the daemon stops with the error it gave earlier.

How can I fix the configuration of the daemon to be in sync with the docker container again?

No one? Pointing me in the right direction for documentation of where the supervisor daemon stores it’s state would also help.

I grepped through the /use/share/hassio but that did not help.

Hmmm running the command “ha supervisor repair” seems to have resolved it. :blush: