Everything posted by flyize
-
Server goes unresponsive daily, but still responds to pings
So I'm running 6.11 now and the server has stayed up, which is great! Thanks for the suggestion @shaunvis! However, my suspicion may be correct as I was able to capture an OOM issue in the logs. By chance can anyone determine what happened? truffle-diagnostics-20230928-0905.zip
-
Server goes unresponsive daily, but still responds to pings
Yep, I'm running it now. Hopefully I can report back tomorrow that its still up and running. I still think it has to be some memory leak somewhere causing OOM to kill everything. That would explain the one time I was able to get into PiHole and see CPU/memory maxed. And sometimes the Home Assistant VM was still available. And *every* time, I could ping it.
-
Server goes unresponsive daily, but still responds to pings
I'm kinda out of ideas. It's been running fine for weeks until this.
-
Server goes unresponsive daily, but still responds to pings
I sure did. The server crashed again but is still responding to pings. This is driving me crazy!
-
Server goes unresponsive daily, but still responds to pings
I'm probably going to curse myself by saying this, but I think it was Plex that was crashing everything. If its still up tomorrow, I'll be confident that its fixed.
-
Server goes unresponsive daily, but still responds to pings
Actually maybe it is Plex https://forums.plex.tv/t/pms-1-32-6-hw-transcoding-issues-and-corrections/853757 They pulled the 1.32.6 release.
-
Server goes unresponsive daily, but still responds to pings
I let it run overnight with everything on but the Plex container and it stayed up. So I just pulled a Plex release from two weeks ago. Seems unlikely that Plex would have some memory leak, but maybe? Does OOM killing things make sense to you?
-
Server goes unresponsive daily, but still responds to pings
Just following up on this. At this point, I cant see how its hardware. If something is eating up all the RAM, couldn't OOM be doing this? Wouldn't that cause things to not work, high CPU, but still have network connectivity?
-
Server goes unresponsive daily, but still responds to pings
Actually now that I think about it, the server is *not* crashing as it responds to pings. Also, one time that I was able to login to the PiHole docker, it showed CPU and RAM maxed. So this doesn't seem like it could be hardware. Unfortunately, I don't have any way to run top or anything to see what's using all those resources.
-
Server goes unresponsive daily, but still responds to pings
My friends and family will kill me. Wait, I just realized that I added a second NVMe for appdata a couple of weeks ago. It's been totally stable, but maybe that's it. I'll remove it. Then try to run memtest. Anything else I can 'actively' run to try and figure out the issue more quickly? edit: Wait, how do I remove the mirrored NVMe?
-
Server goes unresponsive daily, but still responds to pings
Went ahead and removed email addresses. Here it is. Thank you so much for any help.
-
Server goes unresponsive daily, but still responds to pings
Anything PII I should remove?
-
Server goes unresponsive daily, but still responds to pings
Server is down again. Please can anyone help?
-
Server goes unresponsive daily, but still responds to pings
So I think I resolved the master browser issue by letting Home Assistant handle it (since it irritatingly has no way to control it). It's been almost 24 hours and I'm crossing my fingers. Seems really unlikely that fixed it.
-
Server goes unresponsive daily, but still responds to pings
I saw that too. Never noticed those errors before. I'll get that fixed. Probably unrelated though, correct?
-
Server goes unresponsive daily, but still responds to pings
And now Home Assistant is down.
-
Server goes unresponsive daily, but still responds to pings
It just happened again. I can still ping the server, but can't get to web UI or ssh in. However, my Home Assistant VM is still up and running just fine.
-
Server goes unresponsive daily, but still responds to pings
When this happened yesterday, I was able to eventually get Pihole to load, which showed load at like 200 and memory at 100%. Server responds to ping and my Home Assistant VM continues to control devices. I set a syslog mirror, so that (final three hours) and diags are attached.
-
unRAID is unresponsive after a day or so
I don't want to muddy your thread, but my server is unresponsive after a day or two. Responds to pings, but can't do anything else until I reboot.
-
unRAID is unresponsive after a day or so
I just started having this issue as well and have enabled the syslog server to flash. There's three threads on the first page about very similar issues. Is this a regular issue that guys deal with users or are we just unlucky?
-
Dealing with unclean shutdowns
Why is it that these settings aren't maintained through an Unraid upgrade?
-
[Support] omada-controller
No, the default template is wrong. It has directories that are some weird path like /mnt/extrassds or something. That is not a valid path.
-
[Support] omada-controller
I just (re)installed It looks like this is because OP left his non-standard pathing in there for the data/log/etc.
-
'nchan: Out of shared memory' errors filling up syslog.
Can anyone assist? This is really crushing my server.
-
'nchan: Out of shared memory' errors filling up syslog.
Thanks for any help guys! Diags attached truffle-diagnostics-20230724-0921.zip