"NetworkManager not correctly configured" + unsupported state warning #3602
Labels
Comments
|
Host logs (too big for the initial post): |
|
Some day, soon? :-) |
|
There is no obvious trigger for the issues in the logs but it appears that something caused the dbus-broker exhausted some of the quotas. If you have access to the host console (via the developer SSH on port 22222), then it would be interesting to check I notice you're running HAOS 12.4, there was a similar report prior to OS 13.0 release in the Supervisor tracker that manifested differently but the dbus-broker was also in that state - the user reported upgrade resolved after the updates, so I'd suggest to update to the latest OS as well - with the latest version the logs wouldn't be cluttered with the "Deactivated successfully" lines too. And on a side note, to get around the issue with the message length, you can attach a text file to the report - for very long logs it better to use that. |
|
Thanks. In short:
Now that you mention bluetooth: yesterday I was trying to send a command to a SwitchBot (really almost next to the HA server/Pi 4) several times, which took like forever to process. Literally, minutes (instead of usually a few seconds). Tested via smartphone app (no HA involved) which triggered the SwitchBot immediately. So yes it looks like Bluetooth in HA has some serious issues - the question is is this a collateral damage (symptom) now or is it the cause? It's the native Pi 4 chip, no dedicated other bluetooth stick (only bluetooth proxies in ESPHome or Shelly). Bluetooth has been a thing in HA OS as I saw issues regularly in the issue tracker bout that. Yes, now that 13.1 is out (I always skip the .0 and forgot about the 13.1 being available for more than 4 weeks now which I consider quite stable, nothing particular found in the open issues section for 13.0/13.1) I think I will first reboot the host with 12.4 to check everything is working smoothly again, create a backup as always and then update to HA OS 13.1 - and hope to never see this again. Unfortunately home-assistant/supervisor#5187 does not specify which board is used. But I agree, the same symptom is one I suffer from too (one network share not accessible). It's completely irrelevant which HA Core version is used. Also my initial speculation in home-assistant/supervisor#5249 the Supervisor might be the bad guy here is wrong, it's clearly a OS/hardware related thing. So do you see anything relevant in the logs? Otherwise I'd now proceed with (the preparations for) the HA OS 13.1 update. |
|
Please note HA OS has been updated to 13.1 at 2024-09-30 and is running since then. Until now the same Networkmanager issue did not occur (yet), but the I think underlying Bluetooth issues now unfold in the way so many other Pi users experienced them. See home-assistant/core#92379 (comment) for details on this, I hope this helps shedding some light on the Bluetooth issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
Today while trying to do an addon upgrade I discovered an issue I've seen (and fixed by restarting HA OS/the host) before:
home-assistant/supervisor#5249
Addon upgrade didn't do anything. According to supervisor logs, nothing happened.
I restarted the supervisor and was able to perform the addon updates afterwards, but at the same time a problem was raised:
(same for the observer)
...which redirects to https://www.home-assistant.io/more-info/unsupported/network_manager
At the same time,
/config/networkdoes not properly (or at all) show network device information anymore:Meanwhile I'm very sure this is a HA OS issue. As I don't want to run into this on a monthly basis (first occured at 2024-08-14, now today at 2024-09-28), I created this issue with some host logs attached.
I believe this "always" happens after running HA OS for a longer time:
On 2024-08-14 at some point I had to restart the host as the whole system became heavily unusable (unresponsive, CPU at 100 %, load-1 far beyond > 15, everything crazy).
Hopefully someone will pick this up quickly (few hours/half a day at best) before I need to apply the workaround (I fear the host might run into similiar instability issues again) and reboot the host to regain a supported, fully working system. Currently I can very likely dig for logs and test stuff, after the reboot usually everything's gone (
ha host logs -b-1 -n1000gives no logs).What operating system image do you use?
rpi4-64 (Raspberry Pi 4/400 64-bit OS)
What version of Home Assistant Operating System is installed?
12.4
Did the problem occur after upgrading the Operating System?
No
Hardware details
4 usb devices attached
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
Yes, very interesting (captured with `ha host logs -n1000` as the UI limits the output to a quite short period of time). To what I see, everything before "2024-09-28 05:29:*" is quite normal. Then some kind of "thing" (incident) happened and network related stuff broke, please interpret this on your own: --------------------------------------------------------------------------------------------------------- (edit: see next comment(s) as GitHub noted "Comment is too long (maximum is 65536 characters)")System information
No response
Additional information
The text was updated successfully, but these errors were encountered: