Hi,

I have to admit, I am not checking my unraid server on a daily basis. Today I saw a red error from the "FIX COMMON PROBLEMS" Plugins:

 

Out Of Memory errors detected on your server

 

I have not noticed any malfunction from the server and do not know what to do except the recommended reboot of the server from this post: 

 Should I check or do somthing else before rebooting?

 

 

... and I forgot to include the diagnostics

 

If it's a one time thing you can ignore, if it keeps happening try limiting more the RAM for VMs and/or docker containers, the problem is usually not just about not enough RAM but more about fragmented RAM, alternatively a small swap file on disk might help, you can use the swapfile plugin:

 

https://forums.unraid.net/topic/109342-plugin-swapfile-for-691/

Thanks for your answer. I will reboot the server and monitor if this is happening again

Note that if a particular container is set to have a max memory allocation precisely to avoid affecting the rest of the server if it misbehaves and exceeds it it'll also be logged as such even if the server itself never got close to running out of RAM.

Edited June 12, 20233 yr by Kilrah

On 6/12/2023 at 9:13 AM, Kilrah said:

Note that if a particular container is set to have a max memory allocation precisely to avoid affecting the rest of the server if it misbehaves and exceeds it it'll also be logged as such even if the server itself never got close to running out of RAM.

 Is there anyway to see wich container causes the problem? Yesterday I got the same error again "Out Of Memory errors detected on your server".

 

The docker tab suggest, that there is no max memory allocation set:

Every docker seems to have the whole 32gb available

Edited June 22, 20233 yr by bubiman

I found the docker that is causing the problem:

 

but right now I don´t know why this problem occurs. There seems to be pleanty RAM available 

1 hour ago, bubiman said:

but right now I don´t know why this problem occurs. There seems to be pleanty RAM available 

 

Go edit the template for that container, enable advanced mode, and see if a max ram amount is defined in the extra parameters.

On 6/22/2023 at 8:36 AM, Kilrah said:

 

Go edit the template for that container, enable advanced mode, and see if a max ram amount is defined in the extra parameters.

There is no parameter set to limit the RAM amount:

 

This also suggests that RAM is not limited:

Then iobroker is probably occasionally crashing and filling up the entire RAM and getting killed. You could add "--restart=unless-stopped" to its extra parameters, and install netdata. After it happens again watch netdata and see if there was a spike in RAM usage in this or another container.

On 6/23/2023 at 12:34 PM, Kilrah said:

Then iobroker is probably occasionally crashing and filling up the entire RAM and getting killed. You could add "--restart=unless-stopped" to its extra parameters, and install netdata. After it happens again watch netdata and see if there was a spike in RAM usage in this or another container.

Thanks, I have installed netdata and will look into it once it crashed again

I'm having a similar situation after my 6.12.10 upgrade.  Were you able to find the root cause and resolve it @bubiman?