On a couple of occasions over the last week my server has been completely locking up - no access via the webGUi or putty, no response from keyboard plugged in locally but the monitor still shows the server login prompt. The IP wont respond to pings and the router status page doesn't show the server as connected (although the iLo is still connected and accessable).

 

After the last time, I hard reset the server and just ran it as normal but this time I ran "tail -f --lines=200 /var/log/syslog" in a Putty window.

 

It was roughly 36 hrs before it occurred again - the log from the Putty window is attached.

 

I have no experience reading the logs but if I had to hazard a guess I'd say it a memory problem. This server only has the stock 2 GB installed. I had planned on purchasing some more soonish but I'm thinking I might have to make this a priority if I wan't to continue to use my system to its full potential. I am running Plex, Sickrage, Headphones and Transmission as Dockers which I suspect is a tough ask for 2 GB only. Although at 2:58 AM I wasn't using Plex and I don't think any of the other Dockers were doing anything significant but I haven't fully investigated this just yet.

 

My setup is as in my signature although I've stopped Sickrage, Transmission and Headphones (leaving only Plex) to see how things go.

 

I plan on running a memtest overnight tonight (I did two passes when I first got the server around 2 weeks ago which didn't show any problems).

 

If anyone could decode the log for me I'd appreciate it. I'll try and do some digging and see if I can make heads and tails of it myself.

Putty_log_2016-03-24.zip

Definitely looks like insufficient RAM for what you are trying to do.  It could of course be a particular process going a bit rogue rather then an issue with total RAM, although since you only have 2GB installed I would lean towards there being insufficient RAM in the first place.  I think that with v6 that 2GB is deemed the basic requirement for NAS functionality and if you want to run any significant.

 

Once you get 'oom' errors then the results can be a bit unpredictable as it depends on exactly what process is selected as the candidate to be killed.    However I am a bit surprised that the console was inoperative at that point.

Thanks itimpi...

 

I'm looking into more memory now. I'll play around with a few things and continue testing to see if I can narrow down the problem a bit.