Out of Memory Errors detected on your server

[jackfalveyiv]

This popped up in the past few days, curious if I just need to reboot or if something else needs fixing here, thanks in advance.

trescommas-diagnostics-20240124-0809.zip

[JorgeB]

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/

[Michael_P]

1 hour ago, jackfalveyiv said:

curious if I just need to reboot or if something else needs fixing here

 

You should reboot for sure, but you have a crap ton of nginx processes which is what's probably causing your issue - do you leave the unraid gui open in a browser?

 

Jan 23 03:36:10 TresCommas kernel: [  10686]     0 10686    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10687]     0 10687    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10688]     0 10688    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10689]     0 10689    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10690]     0 10690    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10691]     0 10691    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10692]     0 10692    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10693]     0 10693    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10694]     0 10694    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10695]     0 10695    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10696]     0 10696    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10697]     0 10697    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10698]     0 10698    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10699]     0 10699    41862    17198   212992        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  10700]     0 10700    41862    17225   225280        0             0 nginx
Jan 23 03:36:10 TresCommas kernel: [  13506]     0 13506    42166    17528   217088        0             0 nginx

 

[jackfalveyiv]

No, only if I'm working on something.

[Michael_P]

11 minutes ago, jackfalveyiv said:

No, only if I'm working on something.

 

If it keeps happening, start disabling plugins and docker containers

[jackfalveyiv]

Looks like this happened again last night.  Attaching a fresh diagnostic.

trescommas-diagnostics-20240126-1242.zip

[jackfalveyiv]

Noticed the alert firing around 12:58AM and between 4-5AM, turning off my Tdarr processes at those windows to see if that makes a difference before starting to disable dockers and plugins.

[Michael_P]

5 minutes ago, jackfalveyiv said:

Looks like this happened again last night.

 

Find out whatever docker container this is a2e8128f65f8dd826c54af5dc2db004697eaf687028a5162fb213399c95b952e and disable it, or just start disabling them one by one

 

Looks like it goes OOM at around 1530 and 0330 so if there's a scheduled task popping off, that could point to the culprit (TDARR scan?)

[jackfalveyiv]

Looks like that's my nginx docker.  Months back I needed to replace my flash drive, and I've had some weird problems around different dockers at different times.  In most cases (Tdarr, Radarr/Sonarr, Plex) I had to build new dockers but plug in the old configs.  I didn't do that with Nginx.  Is it possible that I need to?

[Michael_P]

2 minutes ago, jackfalveyiv said:

Is it possible that I need to?

 

Probaby, since it's the nginx processes that are chewing up the RAM