Unraid Server Occasionally Unreachable - Need Help Diagnosing

[nikoan]

Hi, I'm experiencing an issue with my Unraid server where it occasionally seems to crash. By "crash," I mean that I can no longer access Unraid itself through the browser using its IP address. However, I can still access certain Docker containers by appending the port number to the IP.

 

For example, SABnzbd displayed an error stating that it couldn't access the directory connected via a volume to the container. Some Docker containers remain functional, but Unraid itself becomes inaccessible, which is quite puzzling to me.

 

I'm attaching the log files hoping someone might spot something I missed.

Does anyone have any idea what might be causing this issue? It happens once or twice a week.

 

Thanks in advance for your help!

mediaserver-diagnostics-20240514-2150.zip

Edited May 15 by nikoan
Improved title

[JorgeB]

Syslog in the diags starts over after every boot, enable the syslog server and post that after a crash.

[nikoan]

I actually did enable the syslog server after the crash before so I hoped the log log now includes the relevant data. Maybe I’ve misconfigured it through if it’s not in there. 

[nikoan]

 

Here is a screenshot of the syslog settings. 

Edited May 15 by nikoan

[JorgeB]

Log should be in the 192.168.178.2 server, alternatively you can enable the mirror to flash drive option.

[nikoan]

Apologies for the confusing remote server setting, it actually is the ip of the server it is about. I’ve now enabled the mirror to flash drive. I’ll answer here the next time the issue happens. Thanks for your help so far. 

[JorgeB]

8 minutes ago, nikoan said:

it actually is the ip of the server it is about

That should work to save locally, and there's nothing in the syslog share?

[nikoan]

I see. Unless I’m completely mistaken then what I’ve uploaded was the contents of the syslog folder. I’ll double check in a few hours and let you know. 

[nikoan]

Apologies again, you were right, I didn't upload the syslog log file but the "bug report" generated files. I'll attach the syslog now.

syslog.txt

[JorgeB]

Unfortunately there's nothing relevant logged, this can be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/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.

[nikoan]

Thank your checking the logs and suggesting the next steps.