Systemd-journal Core Dump on HAOS 12.2 on Proxmox

Hi,
last night I got a Systemd Core Dump on HAOS12.2 on Proxmox:


This caused Home Assistant restart but it is like docker is not able to spin up the container. So i decided to shutdown, and during shut down I got:

Then take lot of time to shutdown:
image

and before shutting down completly i got this:


and stayed on this screen for 5/6 minutes before completly shutdown. After reboot HAOS spin up all services, but I noticed that docker took long time to start, and HAOS took about 5/6 minutes to startup all services.

Any Ideas on what it could happened?

Thanks

1 Like

Had the same on HASS OS 12.3 and Core 2024.5.3 on Proxmox 8.1.11. Shutdown was not possible, had to reset. I noticed a strong rise in CPU Load before and during the hang. Ping was still possible. HA URL, Observer URL, samba share were unreachable. I checked home-assistant.log.1 after reset and found many network connection problems including internal network connection to Mosquitto. Last entries were:

2024-05-14 04:06:45.002 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /info request
2024-05-14 04:06:45.119 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /host/info request
2024-05-14 04:06:45.120 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /store request
2024-05-14 04:06:45.121 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /core/info request
2024-05-14 04:06:45.160 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/info request
2024-05-14 04:06:45.160 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /os/info request

Any update on this? I noticed this behaviour on my VirtualBox too. I cant identify the problem.