-
Notifications
You must be signed in to change notification settings - Fork 677
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
SUPERVISOR - Failed to get logs using advanced API (NEW - NOT THE SAME) #5606
Comments
Can you share the host logs of that system as well?
I wonder if Supervisor crash is just a symptom of a bigger issue. To me it sounds as if the system hangs completely on I/O or something. What do you mean by system cannot be accessed? The Home Assistant Core frontend is also not available? |
Hi Stefan. Thank u so much for saying hi. Its bizzare type of behaviour. Still crashed. Ive left it alone today. And I can say logs are all green. Nothing happened since 10pm last night. When things happen often message relates to aiohttp or websocket.api or journald which all in all looks like a timeouts or rejections in connections. Again its been ok today but we are wondering what could be causing these. These crashes are extreme. Sudden. Unexpected. Finally. Brand new ssd. Brand new haos. And restored backup. One crash pretty much straight after restore…. Ill try to give u any logs u need if u r interested trying to conquer this issue. Just ket me know which parts specifically would help u. I do have screenshots if crashes from the past if these help I am once more very grateful. Raf |
I am getting the very same error on a supervised debian 12 installation with Hass 2025.2.0 and Supervisor 2025.2.0. Additionally I get another random occuring error since Supervisor 2025.2.0. I can't tell what triggers the error since it happens in intervals of 5 minutes to several hours and I don't think it is related to logs, but might be related to a bigger problem. Today, even the whole system rebooted itself after it apparently crashed - I've never seen that before. I can't find anything suspicious in any log, except the OP's error and the one below coming from Supervisor.
|
......................................................................................................................................................................... First crash since rebuild... throughts?
|
has anyone had any more success with all of this? this post has gone quiet.... |
Describe the issue you are experiencing
Hi all
I have read through both previous issues and cases which simply refer to each other and are now closed and limited...
This issue has not been solved from research I have done.
I was told this issue is a similar issue to what happens when a docker is installed, but now I have this issue with bare metal HAOS install.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Steps to reproduce the issue
2.We have rebuilt new NVME 2 Drive and new HAOS and reinstated the backup - same or very similar issue occurs.
...
Anything in the Supervisor logs that might be useful for us?
System Health information
Installation type | Home Assistant OS
Development | false
Supervisor | true
Docker | true
User | root
Virtual environment | false
Python version | 3.13.1
Operating system family | Linux
Operating system version | 6.6.73-haos
CPU architecture | x86_64
Timezone | Australia/Brisbane
Configuration directory | /config
Home Assistant Supervisor
Host operating system | Home Assistant OS 14.2
Update channel | stable
Supervisor version | supervisor-2025.02.0
Agent version | 1.6.0
Docker version | 27.2.0
Disk total | 916.2 GB
Disk used | 28.1 GB
Healthy | true
Supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization |
Board | generic-x86-64
Supervisor API | ok
Version API | ok
Installed add-ons | Matter Server (7.0.0),
Advanced SSH & Web Terminal (20.0.0),
Amber2MQTT (2025.2.4),
AppDaemon (0.16.7), EMHASS (v0.12.4),
EMHASS-GeoDerp-test (test),
ESPHome Device Builder (2024.12.4),
File editor (5.8.0), Git pull (7.14.1),
Mosquitto broker (6.5.0),
WiNet Extractor (0.2.2)
Supervisor diagnostics
No response
Additional information
I would love if this was not just referred to other two issues and closed off... as I cannot find any related answer to the problem.
System is bran new and fresh - only 12 hours old now, since rebuild...
Network doesnt seem to be an issue, we have gone through it yesterday,
I run unify, and over 60 tuya devices communicating on that network and not timing out...
We have removed vscode as it was misbehaving badly and landing a lot of errors...
supervisor appears to be the main and only remaining source of crashes now...
I am not quite sure what drives these though
Any help would be amazing - please.
Thank you in advance - much appreciated.
@purcell-lab
@agners
Raf
The text was updated successfully, but these errors were encountered: