ran check for common problems and I had a few dockers using unassigned drive without setting path to rw/slave.  I cleared all those up but I see trace calls.

 

can someone take a peek and tell me if my server is in danger?
 

pajamaserver-diagnostics-20170626-1454.zip

Edited June 26, 20179 yr by jonnypajamas

Java keeps killing off processes as it is requiring more.  If you've got CrashPlan running, that'll be my primary guess as to the cause (its a pig)  After that, the next cause would be Plex

plex it is.  what can I add to my system to help that out?  

You could try limiting the memory available to your containers to say 4G (add this to all of them).  Also, don't have Plex transcode to RAM.  Plex is my guess, but realistically you have to figure out what was going on at the time of the OOM errors.  All containers will use whatever is available to them.  Things like D/L clients will use all available RAM if they can when unpacking, and if something else needed the memory at the same time, then you're SOL.  

 

That, and you could always upgrade your RAM

 

 

i have plex set to transcode to an unassigned ssd.  My subsonic failed on me, it may have been that which was throwing errors.

6 minutes ago, jonnypajamas said:

i have plex set to transcode to an unassigned ssd.  My subsonic failed on me, it may have been that which was throwing errors.

Its a play thing.  All we know is that whatever app is running that uses Java triggered the error.  But, it may not have actually been the guilty party.  It could be something else.  (Guilty by association?)

SO my system is NOT in imminent danger of catastrophic data loss?

no