You can probably find evidence of this in the system logs, on most modern systems, this should show you higher prio logs from last boot:
journalctl -p4 -b
You should see something like this, if it was killed by OOM killer
MESSAGE=Killed process 3029 (Web Content) total-vm:10206696kB, anon-rss:6584572kB, file-rss:0kB, shm em-rss:8732kB
And you should definitely think about extending the memory of the system or reducing the number of containers/they memory footprint.
The question is not so much if you have enough physical ram but if your docker management tool has established resource limits for the containers. Oom killer will stop the process regardless of the fact that there is enough free memory if the container goes over its Ressource contraints.
Most likely low memory, linux systems when there are out of memory calls the OOM killer, which kills the largest processes running on the system. https://unix.stackexchange.com/questions/153585/how-does-the-oom-killer-decide-which-process-to-kill-first
You can probably find evidence of this in the system logs, on most modern systems, this should show you higher prio logs from last boot:
journalctl -p 4 -bYou should see something like this, if it was killed by OOM killer
MESSAGE=Killed process 3029 (Web Content) total-vm:10206696kB, anon-rss:6584572kB, file-rss:0kB, shm em-rss:8732kBAnd you should definitely think about extending the memory of the system or reducing the number of containers/they memory footprint.
Journactl doesn’t work in unRAID. I don’t thinks it’s a memory problem usually memory usage is around 10-15GB and I have 40gb of memory
The question is not so much if you have enough physical ram but if your docker management tool has established resource limits for the containers. Oom killer will stop the process regardless of the fact that there is enough free memory if the container goes over its Ressource contraints.
https://stackoverflow.com/questions/42345235/how-to-specify-memory-cpu-limit-in-docker-compose-version-3
So do the
journalctl -p 4 -bon the host self.What do you mean with host self?
On the host running unraid.
You can also see oom killer messages with dmesg