#homeassistant crashing

1 messages · Page 1 of 1 (latest)

lofty light
#

so again.. it is crashing again. how do i find a reason why and how it got to this?

what is going on with ram? when cpu goes up then it soon it crashes.

any idea?

#

it is very annoying becouse went zigbee lights way and cant do shit without HA

alpine sail
#

memory leak?? disable custom integrations or start in safe mode, check if memory keeps rising. If not, check integrations one by one (disable) until problem solved.

#

And post logs

#

running haos vm on proxmox as it seems. Do you have music assistant enabled? Are you up-to-date with software?

lofty light
#

but it doesnt look like memory leak.. here on this pic when i gets low it crashed

#

probably if it would not crash it would go to 8gb

#

will be now monitoring integration

#

which logs? there is miltiple logs

#

yes on proxmox 9. it was running fine for months and nothing changed in homeassistant

#

i do not have music assistant enabled and i am on lattest version yes everything updated

alpine sail
#

supervisor/core

lofty light
#

in supervisor i have many:

#

2025-12-27 16:14:48.887 WARNING (MainThread) [supervisor.homeassistant.core] Watchdog found Home Assistant failed, restarting...

#

2025-12-27 16:14:46.071 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed 2025-12-27 16:14:46.270 WARNING (MainThread) [supervisor.api.host] ConnectionError raised when returning journal logs: Connection lost

#

2025-12-27 16:44:51.985 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed! 2025-12-27 16:44:51.036 ERROR (MainThread) [supervisor.homeassistant.core] Watchdog restart of Home Assistant failed!

alpine sail
#

check internal network, dns working? Dont trust proxmox memory indication though.. You can install Glances add-on, disable secure mode and start add-on, then press "m" for showing memory usage. Look if something is eating more memory then usual.

#

If nothing stands out, go to the cli once again and enter root level with login

#

Then you can try to repair supervisor with ha supervisor repair when finished enter ha host reboot

#

Set IP for haos vm static (reservation) in router and leave haos network as Automatic (DHCP) then reboot

lofty light
#

now that im monitoring it it works... 😄 i dont know if it is related but i have turned off one ct in proxmox

#

internal network is ok, dns ok

#

i have static ip for haos.. oh ok will do

#

thank you for all help and ideas