During my weekly scan of the Fix Common Problems Plugin I got the following error message: "Out Of Memory errors detected on your server"

The forum post of the plugin said to post here in the support forum so here I am.

My server is a pretty powerful server, it's running Unraid 7.1.0, has 32 GB DDR5 RAM, XMP / EXPO profile is NOT enabled so RAM is running at base speed. I am running two cache NVMEs SSDs in RAID 1 and 3 Array HDDs with one assigned for Parity.

I have encountered a weird issue three days ago where Docker containers refused to update and my assumption was that the Docker.img file ran out of space so I increased it from the default 20GB to 30GB. After some manual cleanup I managed to update the Containers just fine and the system has been rock stable since then.

So I don't really got any idea where the error could be coming from.

I would appreciate your help, diagnostics attached.

astaroth-diagnostics-20250516-1413.zip

Edited May 16, 20251 yr by Shochraos

54 minutes ago, Shochraos said:

During my weekly scan of the Fix Common Problems Plugin I got the following error message: "Out Of Memory errors detected on your server"

The forum post of the plugin said to post here in the support forum so here I am.

My server is a pretty powerful server, it's running Unraid 7.1.0, has 32 GB DDR5 RAM, XMP / EXPO profile is NOT enabled so RAM is running at base speed. I am running two cache NVMEs SSDs in RAID 1 and 3 Array HDDs with one assigned for Parity.

I have encountered a weird issue three days ago where Docker containers refused to update and my assumption was that the Docker.img file ran out of space so I increased it from the default 20GB to 30GB. After some manual cleanup I managed to update the Containers just fine and the system has been rock stable since then.

So I don't really got any idea where the error could be coming from.

I would appreciate your help, diagnostics attached.

astaroth-diagnostics-20250516-1413.zip 520.74 kB · 0 downloads

 

 

Looks like qbittorrent was running the host OOM for a few days ending on the 14th, if you've since corrected whatever it was doing (probably folder mapped to RAM instead of disk), you can reboot to clear the log so FCP stops warning you. If it happens again, verify your folders are mapped correctly

Folders are mapped correctly, all folders are mapped to either the cache or the array.
Also, all my containers are RAM-limited so technically that shouldn't happen?
Where in the logs did you find the entry?

Or did you mean something else? What exactly means folder mapped correctly? I assume it's that all persistent storage folders are on a drive like Cache or Array drive, yes?

 

Actually, I got a question, if the qBit client runs out of memory if you limit it via the WebInterface / Docker command and it overflows, it also gets killed. Could the entries in the log mean the client reached the memory threshhold?

Astaroth kernel: Memory cgroup out of memory

Thats the line in the syslog that got me thinking about that

4 minutes ago, Shochraos said:

Folders are mapped correctly, all folders are mapped to either the cache or the array.
Also, all my containers are RAM-limited so technically that shouldn't happen?
Where in the logs did you find the entry?

 

May 14 04:48:11 Astaroth kernel: Memory cgroup out of memory: Killed process 3887080 (qbittorrent-nox) total-vm:2118364kB, anon-rss:2074044kB, file-rss:88kB, shmem-rss:0kB, UID:99 pgtables:4180kB oom_score_adj:0

 

it was repeatedly running OOM and killing qbittorent from when your logs started on May 11th until May 14th

Yeah exactly -> the total memory assigned to the container is 2118364kB, which should be the 2GB I assigned in the Webinterface, correct?

So it's actually not my Host system running out of total memory but instead the Docker Container overflowing the RAM

 

Just now, Shochraos said:

So it's actually not my Host system running out of total memory but instead the Docker Container overflowing the RAM

 

 

No, your host is running out of memory and killing what it thinks is using the most memory - and that it's continuously killing qbittorrent, that would be the likely suspect. Doesn't look like it from the logs but are you running any other containers?

Yeah I'm running a lot of containers, around 38 containers

But some of them are databases which use next to no RAM

Heavyweight dockers I'm running are multiple qBits, Jellyfin, Immich, Nextcloud

Just now, Shochraos said:

Yeah I'm running a lot of containers, around 38 containers

 

It might actually just be docker killing it (doing it right for once), hasn't happened in a couple days so I wouldn't worry about it too much - if you have free RAM to play with, allocate a bit more to it or put qbittorrent on a diet so it's not using as much.

Yeah, i've never seen my host system go above 14 Gigs of RAM so its unlikely to be the Host system. I'll give the qBit instance in question 4 Gigs of RAM

Thanks for your patience.

Just now, Shochraos said:

Yeah, i've never seen my host system go above 14 Gigs of RAM so its unlikely to be the Host system. I'll give the qBit instance in question 4 Gigs of RAM

Thanks for your patience.

 

ps -auxf will tell you what's spawning what and the resources it's using, can be helpful tracking down repeat offenders.

Thanks, will do that