I had a power outage a few days ago and noticed that my Home Assistant (HA) environment hadn’t recovered. I was able to manually start the Home Assistant container, but the supervisor keeps looping through image building, starting, crashing, and removing everything.
Today, I spent time reinstalling the supervisor service and updating the host to try and fix the issue. However, any hassio_supervisor image beyond version 12.0 (including the first 12.1 dev version from 4 days later) fails to start and immediately results in an “exec /init: exec format error.” Versions 12.0 and earlier (I tried with 11.4) start without any issues.
Does anyone have a suggestion on how to resolve this issue? Every reboot currently results in the supervisor service immediately updating the supervisor container and looping into the issue until I manually downgrade, which then causes the system to become unhealthy within HA.
You are running a supervised installation.
It is nearly impossible for us to know how your system works.
You need to look at your logs, check all dependencies and then ask questions about specific things.
The supervised installation is too open to be generally supported and you need to understand and be able to deduct much more from your system to get help.
That is the backdraw of a supervised installation.
Thank you for your response. It seems to me related to something changed after the supervisor 12.0 image release since all versions before seem to work and versions after result in the exec /init: exec format error. (even starting blank containers from the images without any configuration). And since this is the only line of logging I get from both the container as docker there is not much to follow-up on.
For any others that might end up here… I’ve created a workaround running the supervisor from the ARMv7 image which is working fine with the :latest tag, and from there was also able to update homeassistant the normal way. Structural solution seems to either start all over again from fresh install or purge and reinstall supervisor on ARMv7 instead of Aarch64.
Somerhing likely changed, but we do not have a huge number of other supervised users in the forum complain about it, so it is something specific to your Debian setup.
UPDATE #2: After a few more crashes, it seemed to be linked to the backups that were running. I removed all of them, except for the nightly backup using the new build in backup and HA Cloud upload. After that there were no more no more crashes. Memory usage is lower, but does still goes up each time a backup is done:
I am using HA on an Intel NUC using the official NUC Image. I have had issues since the last OS on a couple of occasions where supervisor will fail, i then have no way to reboot the machine without doing a hard power off.
I have checked the supervisor logs from the last crash, they simply pause after the host information reload complete message and there was no additional logs until 11:15 today after supervisor failed at 05:14 this morning after taking backups
025-01-24 05:13:01.074 INFO (MainThread) [supervisor.backups.manager] Backup 80e59d98 starting stage folders
2025-01-24 05:13:01.078 INFO (SyncWorker_1) [supervisor.backups.backup] Backing up folder ssl
2025-01-24 05:13:01.088 INFO (SyncWorker_1) [supervisor.backups.backup] Backup folder ssl done
2025-01-24 05:13:01.089 INFO (MainThread) [supervisor.backups.manager] Backup 80e59d98 starting stage finishing_file
2025-01-24 05:13:01.610 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug 80e59d98 completed
2025-01-24 05:13:01.763 INFO (MainThread) [supervisor.api.backups] Downloading backup 80e59d98
2025-01-24 05:13:23.631 INFO (MainThread) [supervisor.api.backups] Downloading backup 80e59d98
2025-01-24 05:14:42.912 INFO (MainThread) [supervisor.host.info] Updating local host information
2025-01-24 05:14:43.940 INFO (MainThread) [supervisor.host.services] Updating service information
2025-01-24 05:14:43.951 INFO (MainThread) [supervisor.host.network] Updating local network information
2025-01-24 05:14:44.272 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
2025-01-24 05:14:44.290 INFO (MainThread) [supervisor.host.manager] Host information reload completed
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
[11:15:39] INFO: Using udev information from host
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)
[11:15:39] INFO: Starting local supervisor watchdog…
s6-rc: info: service legacy-services successfully started
2025-01-24 11:15:41.692 INFO (MainThread) [main] Initializing Supervisor setup
2025-01-24 11:15:41.830 INFO (MainThread) [supervisor.bootstrap] Setting up coresys for machine: generic-x86-64
