Home Assistant (2024.5.1) container random crash

Configuration
1

Hello
I noticed since updating to the latest build of Home Assistant (homeassistant/home-assistant) my HASS crashes randomly with the error message below.

Where do I begin to diagnose this?

I’m assuming that exit code 256 and signal 9 mean something that might help.

[21:05:38] INFO: Home Assistant Core finish process exit code 256
[21:05:38] INFO: Home Assistant Core finish process received signal 9
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
2

What did you update from?

How did you update?

Do you use compose? Provide it, maybe it matters.

Did you try rebooting host?

3

  • I’ve always got the containers from Docker Hub, hence the “homeassistant/home-assistant” above.

  • I updated by doing a “docker compose pull”

  • Relevant compose section:

  hass:
    image: homeassistant/home-assistant
    restart: unless-stopped
    container_name: hass
    hostname: hass
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "$PWD/../certs/common:/certs/"
      - "$PWD/../conf/hass:/config"
    networks:
      - backend
    environment:
       PUID: '2027'
       PGID: '2027'
       DISABLE_JEMALLOC: true
    labels:
      - "traefik.enable=true"
      - "traefik.docker.network=backend_network"
  • I have already tried rebooting the host.
4

Using custom integrations. Try starting without them

Maybe db. Rename it and start it and see if it works.

I would actually start a container with no mounted volumes to make sure I can get that running as default.

If you are basically just using homeassistant:latest, when was last time you updated? A month ago or more? Could be breaking change. Really that or some db problem is only issues that prevent start.

There is nothing obvious from log you provide and just updating from HA:2024.04 to 2024.05 won’t cause problems. In the future I suggest selecting specific tagged versions. Helps to track down problems. For now you can Try the stuff above to help Isolate problem

5
6

Hi,
I have the same problem with HAOS. Do you find a solution ?

Thx

7

I think mine was a RAM issue. I increased the RAM on my device and it almost disappeared. I say almost because it happens occasionally but always while I’m outside the house. Grrrh

1 Like
8

Hello,

I also noticed an OOM (Out of Memory) in the VM’s shell when I was losing access.
I upgraded from 8GB to 12GB, so I hope I won’t have the problem anymore.

Thx for your answer.