Home Assistant restart randomly multiple times a day

Hi,

I have a weird issue with Home Assistant, it restarts multiple times every day

Setup

  • Proxmox VE running on Intel NUC Celeron with 4GB of RAM
  • HASS OS 7.6
  • qemu image
  • 2022.5.01

Supervisor logs:

22-05-12 16:41:09 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config: 
22-05-12 16:41:09 WARNING (MainThread) [supervisor.misc.tasks] Watchdog miss API response from Home Assistant
22-05-12 16:44:11 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config: 
22-05-12 16:44:11 ERROR (MainThread) [supervisor.misc.tasks] Watchdog found a problem with Home Assistant API!
22-05-12 16:44:11 INFO (SyncWorker_2) [supervisor.docker.interface] Restarting ghcr.io/home-assistant/qemux86-64-homeassistant

Another incident here:

22-05-12 17:48:26 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
22-05-12 17:50:57 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config: 
22-05-12 17:50:57 WARNING (MainThread) [supervisor.misc.tasks] Watchdog miss API response from Home Assistant
22-05-12 17:53:28 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config: 
22-05-12 17:53:28 ERROR (MainThread) [supervisor.misc.tasks] Watchdog found a problem with Home Assistant API!
22-05-12 17:53:28 INFO (SyncWorker_1) [supervisor.docker.interface] Restarting ghcr.io/home-assistant/qemux86-64-homeassistant

I don’t know where to start looking, I’d be happy for some assistance.

Thanks,
Jafar

1 Like

Fixed, integration that caused a deadlock was the reason - I hope the infrastructure will be able to handle such incident more user friendly in the future.

1 Like

Hello,
Same problem here how to find integration that cause the issue?

1 Like

Same - which integration was it please?

My HA Pi is STILL randomly restarting. Any idea how I can find out what’s causing this?! No discernible pattern at all. And oddly…the SD card doesn’t seem to get corrupted - which is obviously great but suggests to me that it’s perhaps a graceful restart? However nothing in logs that I can see?

Same, and nothing in the logs. Any ideas?

What integration was it that caused the deadlock and how do you go about troubleshooting? I am having the same issues but do not see anything in the logs.

1 Like

@jafar-atili
Share the solution for this problem so that it will help everyone.
i’m also facing the problem for more than a month, But cont find the proper solution.

1 Like

Same problem for me. Looks like a bug for more users.

Same problem for me. :thinking:

I’d suggest you start disable integration one by one until you get to a state whrer this issue doesn’t reproduce.

In my case it was a custom component I developed, so it was easier for me to understand where the deadlock is

1 Like

Looks like it’s the kernel ?