dockerd is trying to kill homeassistant container #3807
Labels
Comments
|
Can you post complete logs with the context when that happens, without cherry-picking, and including Supervisor logs? The log lines indicate that a graceful shutdown was requested through the Docker API (not obvious from the logs when) and the Core container is not responding to then, then it's not responding to a kill signal either. There should be something that requested the restart, and it can't be OOM killer, because that would kill a process without calling the API. Also, the question is why the container doesn't react to the shutdown signals, Core logs may be helpful here too. |
|
So, I came back with more logs. This issue appeared once again and now I can show you more logs I case you want to trace the timedate in logs Logs of Don't bother with logs from camera. I tried something A large snapshot of Docker shows that Logs of Other information where I tried to investigate the issue From information of I am working with docker from some time and I had bad experience with this kind of behavior, to have zombie processes in the container, therefore it won't let me to stop gracefully a container or to restart it. I started to use I tried to restart it manually, it doesn't work: I think the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
Hi team,
I am using HA as OS installed on an Intel NUC (4 Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz, x86_64, 8 GB RAM). HA version is
2024.12.1,ha os infooutput:ha host infooutut:My worrying problem is that I caught when
dockerdis trying to kill thehomeassistantcontainer. Here are the logs from host (ha host logs):Here is the proof that container id matches with the
homeassistantcontainer id:The other services was working.
Cloudflare&Netcloudare part of my addons installed. I succeeded to access my Nextcloud over internet through TCP tunnel (created my Cloudflare addon). So, that means the host was working. Unfortunately I don't have more logs to see what happened before killing signal and why dockerd decided to send a stop/kill signal to homeassistant container. I restarted the host with force.I am not sure if I would blame
OOM Killerfor that signal, from this graph you can view that I have enough RAM memoryWhat do you think, guys ?
Next time I will be more prepared to investigate when this problem will occur.
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
14.0
Did the problem occur after upgrading the Operating System?
No
Hardware details
4 Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz, x86_64, 8 GB RAM
Steps to reproduce the issue
Hard to say
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
Additional information
No response
The text was updated successfully, but these errors were encountered: