Hello, 

I'm trying to figure out this issue, it's been happening a couple times over the last week.  Randomly I will go to do something on the server, and its not reachable anymore, like the server IP just times out.  I can't access any of my dockers anymore either.

The server itself is still on, but I just can't reach it.  This seems to be happening more frequently and am not sure what I need to do to address it.

I have attached my diagnostics with the hopes that something shows there as to what is causing it to occur.

 

Thanks

plex-diagnostics-20230928-0931.zip

Enable the syslog server and post that after a crash.

12 minutes ago, JorgeB said:

Enable the syslog server and post that after a crash.

Thanks, I have enabled it and set it to remote to my 2nd unraid server.

This might be related to the same issue, it might not.  But the server just randomly rebooted and started a parity check. I have syslog server enabled.  Do I still just pull a diagnostics, and it knows where it get the data from the syslog server, or how does that work?

Here is the diagnostics if so.

plex-diagnostics-20231006-1004.zip

24 minutes ago, coltonc18 said:

But the server just randomly rebooted

If it really rebooted, vs hanging or crashing, it's likely a hardware problem.

14 minutes ago, JorgeB said:

If it really rebooted, vs hanging or crashing, it's likely a hardware problem.

Yeah, this time it did reboot, just wasn't sure if they were related or not.  Does anything in my stuff show what the hardware problem might have been?

Hardware issues don't usually leave anything logged, you can try running memtest, if you have a different PSU also try that.

Ok, sorry back again. 

 

The server just did the hang up where it doesn't restart, but is just unreachable. 

 

Here is the diagnostics. I'm not sure if I need something else to access the syslog server data. 

 

Thanks! 

plex-diagnostics-20231008-1318.zip

13 hours ago, coltonc18 said:

I'm not sure if I need something else to access the syslog server data

You need to get form where it's being saved, it doesn't come with the diags.

I think I had this all setup wrong the whole time...Is this how I need to set this up?

The first pic is the machine I am trying to get the data from.

This is the machine I am trying to get to record the data....I had it setup completely different before, but after reading around...I think this is right now?

or do I need it on for "local syslog server" on the machine im trying to get the data from as well? 

You need to set the remote syslog server IP, use the local server IP, or just enable the mirror to flash drive option.

ok, got it now....its generating logs, i'll report back once I get another freeze.  Thanks for the help.

Edited October 9, 20232 yr by coltonc18

I came in this morning, and noticed it was in that state, not sure exactly when it happened overnight....but here are the logs that have been storing on the other server.

Thanks

syslog-192.168.1.9.log

Call traces look similar to these, see if this applies to you:

 

2 hours ago, JorgeB said:

Call traces look similar to these, see if this applies to you:

 

Thanks for this, I ended up changing that container over to this.  We'll see if this helps-- binhex/arch-delugevpn:libtorrentv1

Sorry to say, it looks like that did not correct my error. Or if it did, I have multiple errors. 

 

I also did a memory test, and changed out the Psu yesterday. 

 

It just happened twice in the last hour or so while watching a show on it. 

 

Here is the most recent log. I will also note, something strange is also happening. Sometimes when it reboots, all drives show as missing except for like 3 of them. It requires a full reboot to fix that. 

 

I've been trying to read these logs right after this happens and I don't see anything, so I'm not sure where to start with this. 

 

Thanks for your assistance here. 

 

-Chase 

syslog-192.168.1.9.log

Unfortunately there's nothing relevant logged in the last couple of days, this usually points to a hardware issue, 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.