My server has been running great for months on end without a hiccup but in the past week I have come home to find it unresponsive and requiring a hard reboot to get it going again. I got my syslog and it looks possible there is something going on with nginx but let me post it here and hopefully someone can help me with what to do or what it means. 

 

I copied between the end of the 12th when it first did it and the beginning of the 14th when it did it again. Let me know if I need to send more. 

 

syslogsnippit.txt

Nothing relevant logged there, post the diags mostly to see the hardware used.

Thanks for taking a look 

tower-diagnostics-20230214-1801.zip

No known issues that I know of with that hardware, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Locked up this morning again, just for good measure here's an updated sys log..

 

 

I'm not sure if this happened before these incidents started or after but I did mess with my sabnzbd docker and messed up a file path that caused my docker to dissappear. I added the docker again and used the already saved configuration that pulled right up from the old one and fixed the file path and that docker works.. but is it possible that old docker is still running but I can't see it?

syslogsnippit (1).txt

Still nothing relevant logged.

The last time this happened to me was when we had a power hiccup... Is your server behind a UPS?

No it is not

You might consider it... It would give peace of mind...

 

next time it happens plug up a monitor to the machine and see if the console is responsive 

 

For me. The machine was still up and running but the console was blank... a restart later with a UPS helped...

Yeah I do have one I can use. 

 

I have a monitor hooked to it and it's a blank screen when it does it power on fans running but nothing on the monitor.. its not running in gui mode as the monitor it's hooked to is actually a tv  but no text is present on the screen.

 

After the suggestion above I have turned off all of my dockers except plex and my vms are offline today as I was out of time to get to work this morning I didn't reboot into safe mode but maybe this will tell me something. If it halts again today as now it has become an everyday thing I will do safemode like I should have per suggestion but if it doesn't I will narrow it down to it maybe being my sabnzb docker conflicting as that the only thing I have changed recently and everything else has been going for almost six months with only restarting for updates. 

 

I know I have not completely done what was requested and when I have time this weekend I will but I noticed something and figured it might be useful to bring up. 

 

Unfortunately disabling all the dockers except plex did not do the trick however I had a friend Watching a marathon of a show and the server did not go unresponsive and unreachable until after he was done and it was left idle.. it also has never done it while a parity check was going  not until after it was complete.. it only ever seems to do this when it goes idle.. 

Could this be something? 

 

For quick reference this processor is a a10-7870k 

Edited February 16, 20233 yr by robotdog

Try disabling C-States in the BIOS.

Unfortunately that didn't work.. woke up this morning checked on the server to see my cpu at 99% still working on parity check then go unresponsive while I navigated the unraid ui on my phone.

When I rebooted into safe mode to give that a try for real and just use it as a nas as suggested. It started with the array offline so I started it and it appears to have started all of my dockers aswell.

This doesn't seem correct did that just mess up safe mode? 

System hung up again as I had this setup going immediately after the last hang up I went into bios so see cpu at 64c and start climbing to 77c cpu fan is spinning. Quick Google search shows it should throttle at 74 I belive and shouldent operate for long above that. Also saw online that there is a chance thats just a bad sensor which apparently is a notorious issue, so started unraid once more in safe mode and currently leaving array offline. 

 

I guess I will let it be for now and see what happens.. looking like hardware issue now. I will mark as solved if it halts again in this state.

Edited February 17, 20233 yr by robotdog

42 minutes ago, robotdog said:

This doesn't seem correct did that just mess up safe mode? 

Docker containers still work in safe mode, you need to manually stop the service.

Thanks in safe mode, have all dockers shut down and the array live now. Also noticed in docker advanced view you can see individual cpu usages. So that will likely come in handy.

Hmm officially safemode including having plex offline which was the only docker we left open last time. We also have full parity no crash I'll keep you updated but so far we are farther then usual before crash

Edited February 18, 20233 yr by robotdog

Currently 11 hours with no dockers 11 hours with all dockers except for plex and we are currently 5 hours with everything and plex going for 27 hours up time which is more than any day this week where it seemed to crash after the 11 hour parity scan everytime. 

 

I did turn off automatically checking for updates to the file system and turned it back on to daily checks. If this works I will try changing that back and see if that was what caused it in the first place. 

 

I guess potentially my last question is once I have turned all of my dockers back on am I still in safe mode and need to reboot or am I back up and running and safemode was just a mode that shut all of that off by default?

Edited February 18, 20233 yr by robotdog

I think I have narrowed this problem down to the plex docker.. is there a log file for this I might be able to open and find out why this issue is happening? 

 

Also is there a way to stress test unraid so I can make sure its not just from heavy cpu usage from plex or something that could end up being triggered by something else in the future?

Before getting up and running with unraid I did do 2 full days of prime95 stress test to make sure ram was good. So I'm wondering If there is something else.

On 2/18/2023 at 7:26 AM, robotdog said:

am I still in safe mode and need to reboot

On 2/17/2023 at 4:21 AM, JorgeB said:

Docker containers still work in safe mode

 

SAFE mode just doesn't load any plugins. You have to reboot.

26 minutes ago, trurl said:

 

SAFE mode just doesn't load any plugins. You have to reboot.

Oh yeah forgot to update the post for that.  its been rebooted, a few hours into having plex open after that post it crashed..  have since rebooted in regular mode and tried it with plex on again to a crash again. Now a full day and 13 hours without a crash in regular mode with everything on except my binhex-plexpass docker. 

Edited February 22, 20233 yr by robotdog
Edited for clarity.

Is plex trying to use gpu?

Thanks for the reply.

 

It would only do that if hardware exceleration under transcoding was selected right?

 

If so that is not turned on.

 

Edited February 22, 20233 yr by robotdog

32 minutes ago, robotdog said:

It would only do that if hardware exceleration under transcoding was selected right?

right