ive been getting these for like 6 months now and was sure a docker or dockerd was causing it because as soon as i killed random dockers OR simply restarted the docker service via ssh, everything starts working again. here is a list of things i have tried:

-safe mode

-cpu pinning to use only the last two on all dockers

-Extra Parameters: -cpus=".5" --memory=4G on all dockers

-deleted the docker image and setup all dockers manually again (not from a restore or using existing templates)

-i also changed ipvlan in docker settings

 

nothing seems to work and with this latest unraid update at least its telling me to post here with the diagnostics so hoping i get some sort of assistance

server-diagnostics-20240419-1340.zip

Looks like the OOM is being causes by Prowlarr, it was using a lot of RAM, I assume the RAM usage is already limited for that container?

15 hours ago, droopie said:

-Extra Parameters: -cpus=".5" --memory=4G on all dockers

 

And verify you have two dashes front of cpus (--cpus=".5")

3 hours ago, Michael_P said:

 

And verify you have two dashes front of cpus (--cpus=".5")

yes just verified it does have the two dashes

6 hours ago, JorgeB said:

Looks like the OOM is being causes by Prowlarr, it was using a lot of RAM, I assume the RAM usage is already limited for that container?

yes i also but weirdly i never actually see the ram in unraid go over 40% but when this happens its always the cpu at 100% even tho i have all the dockers to skip the first pin pairing and use the last 2 only. could it be faulty ram? i havnt had issues with OOM since building it in 2019

9 hours ago, droopie said:

could it be faulty ram

 

Nah, Prowlarr was using ~11GB when it was killed by the reaper so something is wrong with it

6 minutes ago, Michael_P said:

 

Nah, Prowlarr was using ~11GB when it was killed by the reaper so something is wrong with it

thanks for the reply! i didnt know it reached that high since i have been using docker stats to see the cpu and ram used by dockers but i have never seen any docker use over 4gb of ram so its good that it did show that. any suggestions on what to do next? 

Just now, droopie said:

any suggestions on what to do next? 

 

If you're limiting it in the container settings, it didn't work   The only other thing is to figure out why it's using so much, bad config or bad install. You can blow it up and install from scratch to see if that does it.

On 4/20/2024 at 7:30 PM, Michael_P said:

 

If you're limiting it in the container settings, it didn't work   The only other thing is to figure out why it's using so much, bad config or bad install. You can blow it up and install from scratch to see if that does it.

I completely reset up most dockers fresh without using any backup. I even made a user script to restart dockerd and the problem still happens. My main issue is I have to go into ssh to stop the dockerd to make webui accessible again so I can safely restart the whole system. I'm out of ideas besides new cpu, mobo, ram.

16 hours ago, droopie said:

I'm out of ideas besides new cpu, mobo, ram

 

It's almost certainly not hardware related, tho adding RAM may help (or the swap file plugin)

Edited May 2, 20242 yr by Michael_P