robotdog

I have resolved the problem. It was due to the scheduled tasks plex did between 2am and 5am but it was not really a plex issue as it appears I just needed to blow the dust out of my server because it was locking up due to overheating the cpu. It would be awesome If someone would make a cpu stress test docker because that would have lead me to my answer way faster (i spent a day running memory test to rule out a bad stick but every thing was good).. I guess plex is the only thing I'm running that put enough stress on the cpu. Been running for a couple days now with plex going and all of my scheduled tasks back turned on.

Not sure who you were replying to but I'm giving this a try and chose 1.31.0.6654-1-01 to go back to from 22 days ago it built the container and started without a hitch.. since my issue just started in the past couple weeks I think this might just work for me. Would this also work to migrate from the plexpass version to the regular version because that's what I was about to try to do to solve my problem but didn't want to rebuild my library.

Did not work. Unresponsive this morning

Good question is there a way to turn that off to find out if it solves my problem? Edit incase anyone else needs to know it's settings/server/library generate credits video markers I also turned off intros just incase.. mine was set to as a scheduled task so I do think there is a good chance that would explain why it always seemed to happen around the same time. Hopefully this does it.. the only good thing about this problem is I will definitely know if it worked by tomorrow morning.

Thanks for the reply. It would only do that if hardware exceleration under transcoding was selected right? If so that is not turned on.

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.

Since the middle of last week if my plex pass docker is running my server will run for about 11 hours or so and then freeze until a hard reboot is preformed. This docker had been running flawlessly since July and I can't figure out what I could have changed or what to do to fix it. If I turn off plex pass, my server will run for days.

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.

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?

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

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.

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.

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

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.

No it is not

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

Thanks for taking a look tower-diagnostics-20230214-1801.zip

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

I Will also note after this last post the server went unresponsive again. While pulling things apart I noticed the front 200mm fan in my case had stopped operating. I Just added a new intake 140mm fan to the side and manually spun the 200mm which got it going though it is clicking so its on its way out.. I don't have another of the same size to replace at the moment But If I don't get another lock up this might have just been an overheating issue. Is there a way to confirm that in the diagnostics or logs? I attached the diagnostics zip anyhow just in case. tower-diagnostics-20220710-0742.zip

I had everything setup and running for a two weeks without a hiccup but for the past week my server goes unresponsive. Usually after it hasn't been used for a while. One time while trying to trouble shoot it happened multiple times and by the time I corrected my syslog server configuration issue that would allow me to retrieve the log it didn't have an issue for a few more days. Woke up early today and unresponsive but still powered on like usual.. I force restarted it with the power button and I downloaded the syslog. I'm hoping someone here can help with that info as I'm not sure what to check and I don't see anything too crazy that I understand in the log. I have run the memtest98+ for 10 passes with no errors. My system is quite old so this took almost 2 days While I was relieved with this outcome I almost had hoped it to be a memory issue. I Attached my syslog.. I only noticed while trying to read it that my server was set to the wrong time zone I'm not sure if that is what the log was reporting but i have now resolved that. I couldn't figure out in the log where the freeze happened. syslog-192.168.1.211.log