Last night FCP started dishing out this error:
 

Quote

Out Of Memory errors detected on your server. Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the Unraid forums.

I have 80GB of total RAM, and usually about 60GB free most of the time, including right now as I type this, so I don't understand what could've used it all up. I have no idea where to even start looking in the diagnostics, so if anyone could help me or point me in the right direction, I'd appreciate it a lot.
I've attached my diagnostics below.

 

Edited February 6, 20251 yr by MyNameHand

You have a lot going on in there, and it's killing different things each time it runs OOM, sonar, qbittorent, python3 - might have something to do with your tdarr instance, but can't be sure with those logs

 

save the output of  ps auxf > ps.txt and have a look at what container is spawning what - if you scrub any usernames and passwords from that file, you can post it here

 

 

1 hour ago, Michael_P said:

You have a lot going on in there, and it's killing different things each time it runs OOM, sonar, qbittorent, python3 - might have something to do with your tdarr instance, but can't be sure with those logs

 

save the output of  ps auxf > ps.txt and have a look at what container is spawning what - if you scrub any usernames and passwords from that file, you can post it here

 

 

Thanks for the reply. Hopefully I didn't miss anything, but I didn't find anything compromising. Here's the file.

 

Edited February 6, 20251 yr by MyNameHand

10 minutes ago, MyNameHand said:

Thanks for the reply. Hopefully I didn't miss anything, but I didn't find anything compromising. Here's the file.

ps.txt 77.81 kB · 0 downloads

 

Qbittorrent is using quite a bit of RAM, but nothing else is jumping out at me. Reboot to clear the log, and if it happens again start by checking the config for it to make sure it's not storing files in RAM. The next step would be limiting RAM available to the containers.

8 minutes ago, Michael_P said:

 

Qbittorrent is using quite a bit of RAM, but nothing else is jumping out at me. Reboot to clear the log, and if it happens again start by checking the config for it to make sure it's not storing files in RAM. The next step would be limiting RAM available to the containers.

Yeah, I have like 3100 torrents, so that's prob why lol. I'll try your suggestion. Also, prob worth nothing my friend just told me that last night while watching on my plex it died about 10 mins before I got the first OOM error.

1 minute ago, MyNameHand said:

Yeah, I have like 3100 torrents, so that's prob why lol. I'll try your suggestion. Also, prob worth nothing my friend just told me that last night while watching on my plex it died about 10 mins before I got the first OOM error.

 

If the plex scheduled maintenance was scheduled around the same time, that may be a clue, too - the media scanner can run away if it chokes on a file and run the host OOM

13 minutes ago, Michael_P said:

 

If the plex scheduled maintenance was scheduled around the same time, that may be a clue, too - the media scanner can run away if it chokes on a file and run the host OOM

Maybe, but I have plex scheduled to run tasks at 06:00, while the error occurred earlier at 04:47. Apparently my friend was in a watch together with another friend, and looking at tautulli, there were 4-5 people total watching at the time. Honestly, I've had more simultaneous streams before, so I doubt the number of streams was the issue. However, I just remembered I do have ram transcoding enabled, so that could the cause.

1 hour ago, MyNameHand said:

However, I just remembered I do have ram transcoding enabled, so that could the cause.

Strong possibility