Hi Everyone,
I have an issue which happened to me twice lately.
I randomly have HA going off, restart the host ( raspi4B) does fix it. But still an issue for me since I cannot have my instance off randomly while I’m away 
I can see in my logs these issue are caused by supervisor “automatic update”
ct 14 18:54:48 optimus systemd[1]: hassio-supervisor.service: Deactivated successfully.
Oct 14 18:54:48 optimus systemd[1]: hassio-supervisor.service: Consumed 1.791s CPU time.
Oct 14 18:54:53 optimus systemd[1]: hassio-supervisor.service: Scheduled restart job, restart counter is at 1.
Oct 14 18:54:53 optimus systemd[1]: Stopped hassio-supervisor.service - Hass.io supervisor.
Oct 14 18:54:53 optimus systemd[1]: hassio-supervisor.service: Consumed 1.791s CPU time.
Oct 14 18:54:53 optimus systemd[1]: Starting hassio-supervisor.service - Hass.io supervisor...
Oct 14 18:54:53 optimus docker[4698]: hassio_supervisor
Oct 14 18:54:53 optimus systemd[1]: Started hassio-supervisor.service - Hass.io supervisor.
Oct 14 18:54:54 optimus hassio-supervisor[4707]: [INFO] Supervisor image has been updated, destroying previous container...
Oct 14 18:54:54 optimus hassio-supervisor[4734]: hassio_supervisor
Oct 14 18:54:54 optimus hassio-supervisor[4707]: [INFO] Creating a new Supervisor container...
Oct 14 18:54:55 optimus hassio-supervisor[4744]: WARNING: The requested image's platform (linux/arm64) does not match the detected host platform (linux/arm/v8) and no specific platform was requested
Oct 14 18:54:55 optimus hassio-supervisor[4744]: 9997ba6ca0f4c31cd234873dea76ba2f1b8219e6ae6e94e49a186079986d00e2
Oct 14 18:54:55 optimus hassio-supervisor[4707]: [INFO] Starting the Supervisor...
Oct 14 18:54:56 optimus hassio-supervisor[4755]: hassio_supervisor
Oct 14 18:54:56 optimus hassio_supervisor[1239]: s6-rc: info: service s6rc-oneshot-runner: starting
Oct 14 18:54:56 optimus hassio_supervisor[1239]: s6-rc: info: service s6rc-oneshot-runner successfully started
Oct 14 18:54:56 optimus hassio_supervisor[1239]: s6-rc: info: service fix-attrs: starting
Oct 14 18:54:56 optimus hassio_supervisor[1239]: s6-rc: info: service fix-attrs successfully started
Oct 14 18:54:56 optimus hassio_supervisor[1239]: s6-rc: info: service legacy-cont-init: starting
Oct 14 18:54:56 optimus hassio_supervisor[1239]: cont-init: info: running /etc/cont-init.d/udev.sh
Oct 14 18:54:56 optimus hassio_supervisor[1239]: [16:54:56] INFO: Using udev information from host
Oct 14 18:54:56 optimus hassio_supervisor[1239]: cont-init: info: /etc/cont-init.d/udev.sh exited 0
Oct 14 18:54:56 optimus hassio_supervisor[1239]: s6-rc: info: service legacy-cont-init successfully started
Oct 14 18:54:56 optimus hassio_supervisor[1239]: s6-rc: info: service legacy-services: starting
Oct 14 18:54:57 optimus hassio_supervisor[1239]: services-up: info: copying legacy longrun supervisor (no readiness notification)
Oct 14 18:54:57 optimus hassio_supervisor[1239]: services-up: info: copying legacy longrun watchdog (no readiness notification)
Oct 14 18:54:57 optimus hassio_supervisor[1239]: [16:54:57] INFO: Starting local supervisor watchdog...
Oct 14 18:54:57 optimus hassio_supervisor[1239]: s6-rc: info: service legacy-services successfully started
Oct 14 18:55:03 optimus hassio_supervisor[1239]: 2024-10-14 16:55:03.289 INFO (MainThread) [__main__] Initializing Supervisor setup
Oct 14 18:55:03 optimus kernel: hassio: port 2(veth87a76a5) entered blocking state
Oct 14 18:55:03 optimus kernel: hassio: port 2(veth87a76a5) entered disabled state
Oct 14 18:55:03 optimus kernel: hassio: port 2(veth87a76a5) entered blocking state
Oct 14 18:55:03 optimus kernel: hassio: port 2(veth87a76a5) entered forwarding state
Oct 14 18:55:05 optimus hassio_supervisor[1239]: 2024-10-14 18:55:05.442 INFO (MainThread) [__main__] Setting up Supervisor
Oct 14 18:55:07 optimus homeassistant[1239]: s6-rc: info: service legacy-services: stopping
Oct 14 18:55:07 optimus homeassistant[1239]: s6-rc: info: service legacy-services: stopping
Oct 14 18:55:24 optimus homeassistant[1239]: [16:55:24] INFO: Home Assistant Core finish process exit code 0
Oct 14 18:55:24 optimus homeassistant[1239]: [16:55:24] INFO: Home Assistant Core service shutdown
Oct 14 18:55:24 optimus homeassistant[1239]: s6-rc: info: service legacy-services successfully stopped
Oct 14 18:55:24 optimus homeassistant[1239]: s6-rc: info: service legacy-cont-init: stopping
Oct 14 18:55:24 optimus homeassistant[1239]: s6-rc: info: service legacy-cont-init successfully stopped
Oct 14 18:55:24 optimus homeassistant[1239]: s6-rc: info: service fix-attrs: stopping
Oct 14 18:55:24 optimus homeassistant[1239]: s6-rc: info: service fix-attrs successfully stopped
Oct 14 18:55:24 optimus homeassistant[1239]: s6-rc: info: service s6rc-oneshot-runner: stopping
Oct 14 18:55:25 optimus homeassistant[1239]: s6-rc: info: service s6rc-oneshot-runner successfully stopped
The point is I don’t get what’s going wrong on this supervisor restart.
The hassio-supervisor service is still up and running, when checking at ‘docker ps’ I can see the home-assistant container is not running and I don’t understand why it doesn’t restart
Any one experienced something like this ?
Cheers