New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Report: Supervised system is reported as Unhealthy system - not privileged every time after supervisor upgrade. #342
Comments
The main issue this is being tracked under is home-assistant/supervisor#4381 it appears to happen only under bookworm and no root cause has been identified yet, the only thing I can say for certain is it seems to happen whenever the container is recreated and resolves itself with a restart, until the next supervisor update when the container is recreated yet again. |
thanks for confirming @ikifar2012. So it seems, at least at this point, I would ask the maintainers for a system state that will report this unhealthy state - something that I can send an alert on, and track. |
See home-assistant/supervisor#4839 for my investigation of what concerning-things seems to be happening here |
The "short" version of that is after a reboot with an existing
|
Thus there appear to be two important issues:
|
I think I ended up leaving it out of the version posted in there, but its perhaps worth noting that with the profile applied, so the problem seems to be potentially less the ( |
speaking to OP's workaround: For my part Conversely, while I was writing home-assistant/supervisor#4839 I could have sworn at some point a "soft" restart was initally but not repeatably sufficient to get from "good" to "bad" (but that could, for example, be something like Footnotes
|
but stopping my thread-spamming, I would be very curious whether other people experiencing this sort of issue can replicate (or countermand) my catching the processes unconstrained (using |
I just installed hassio supervised on a fresh debian (bookworm) system and happy to help debug, but much of this thread is over my head. What I can say with certainty is:
This was also my experience. Happy to run any commands and provide their output for corroboration. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
home-assistant/version#370 fixed home-assistant/supervisor#4381. |
I would fully expect so, but you know, it needs to roll out first for what it’s worth I belatedly applied my suggested workaround of pulling the profile entirely and haven’t had an issue since, though technically that’s a different thing |
Still awaiting this home-assistant/version#372 to be merged as well... We will see after the next supervisor update |
OS Version
Debian GNU/Linux 12 (bookworm)
System Information
Linux ha 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux
What happened?
Whenever the supervisor is updated, the Unhealthy system - Not privileged.
Resolving this is easy, all I need to do is to restart the supervisor service from the OS prompt - I actually have a cron job that does it one a day.
I've been reading the threads, and I was not able to pinpointed the root cause of this issue.
This bug report has 2 goals:
The only method I have right now is:
It works, but very crude. I put it in a cron job as this has become really annoying.
Machine Type
generic-x86-64
Installer output
Relevant log output
ADR
Code of Conduct
The text was updated successfully, but these errors were encountered: