This morning at 4:40 my server has run out of memory, and I have no idea why. The server is not active in that period, and does not use ressources.

 

I have looked through the logs, and the only enrty at the time was:

Aug 13 03:03:02 Thor Plugin Auto Update: Checking for available plugin updates
Aug 13 03:03:07 Thor Plugin Auto Update: community.applications.plg version 2019.08.11b does not meet age requirements to update
Aug 13 03:03:08 Thor Plugin Auto Update: Community Applications Plugin Auto Update finished
Aug 13 03:03:42 Thor kernel: mdcmd (58): spindown 0
Aug 13 04:40:02 Thor root: Fix Common Problems Version 2019.06.30a
Aug 13 04:40:02 Thor root: Fix Common Problems: Warning: Docker Application binhex-jackett has an update available for it
Aug 13 04:40:02 Thor root: Fix Common Problems: Warning: Docker Application binhex-nzbhydra2 has an update available for it
Aug 13 04:40:02 Thor root: Fix Common Problems: Warning: Docker Application EmbyServer has an update available for it
Aug 13 04:40:02 Thor root: Fix Common Problems: Warning: Docker Application PuTTY has an update available for it
Aug 13 04:40:12 Thor root: Fix Common Problems: Error: Out Of Memory errors detected on your server
Aug 13 05:24:16 Thor autofan: Highest disk temp is 35C, adjusting fan speed from: 42 (16% @ 0rpm) to: 50 (19% @ 385rpm)
Aug 13 05:55:01 Thor Docker Auto Update: Community Applications Docker Autoupdate running
Aug 13 05:55:01 Thor Docker Auto Update: Checking for available updates

 

Please help. I cant figure out what goes wrong.

I have attached zip file for diagnostics.

 

thor-diagnostics-20190813-0650.zip

The log you quoted is when the FCP plugin telling you that there WAS an OOM error on your server. It's not the timestamp of when the error happened.

You had OOM errors on these time stamps:

• Aug 12 09:44:31 
• Aug 12 09:44:31 
• Aug 12 13:18:52 
• Aug 12 13:21:22 
• Aug 12 13:24:13 
• Aug 12 13:27:43 
• Aug 12 13:33:33 
• Aug 12 13:39:09 
• Aug 12 13:46:12 
• Aug 12 13:53:01 
• Aug 12 14:01:44 
• Aug 12 14:10:04 
• Aug 12 14:18:17 
• Aug 12 14:28:35 
• Aug 12 14:39:17 
• Aug 12 14:52:36 

It looks to be all by docker a42f60d82242a9af576f67954002ad97b0c1f2e70e603a58ac3e7cb02cfb2e83

 

Go to Docker tab, click the toggle next to "BASIC VIEW" to enable "ADVANCED VIEW". Under each docker you will see Container ID.

Container ID only has the 1st 12 characters but it should be enough for you to match it to the problem ID above.

 

 

 

 

I looks like its this container

 

I have limited the container, so how can it use all memory on server?

Or does the error indicate the container maxes out my limit on 512MB?

11 minutes ago, thostr said:

I looks like its this container

 

I have limited the container, so how can it use all memory on server?

Or does the error indicate the container maxes out my limit on 512MB?

The latter i.e. it maxes out your 512MB limit.

3 minutes ago, testdasi said:

The latter i.e. it maxes out your 512MB limit.

Thank you for clarifying.

 

I have removed the limit. Hopefully it will clear things out

I just found this topic and i think its the same problem i have been having also i have figured out based on following whats happened here that my plex media server is the issue the docker it seems and happens every sunday morning at 430am. I just cant figure out why its happening because its been given the ability to use up to 24gb of memory. I do run ram transcoding through plex but nothings ever being transcoded at the a time or even being watched and its been happening for the last few months now i wasnt sure if maybe you can shed some light onto where i can go to find the answer because i kinda strugging since im not sure what plex could possibly be doing with 24gbs or ram to be killed by unraid