Unraid Server becomes unresponsive

[Verizon]

Hi,

 

i´ve the issue that my unpaid server becomes unresponsive once in one or two weeks, the docker images are no longer running and also the management interface is no longer reachable. I therefore activated the loging and had a look in the log, however I'm not able to determine where is the issue. Could you please help me with it?

 

Attached you can find the log.

 

Thanks in advance, best regards Daniel

syslog-10.10.10.100.log

[ich777]

35 minutes ago, Verizon said:

Could you please help me with it?

Please include the full Diagnostics, this is only a snippet from the syslog that you've provided.

The Diagnostics are essential to troubleshoot such issues.

[Verizon]

Hi,

 

attached you can find the diagnostics.

 

Best regards Daniel

dcap-diagnostics-20230907-1006.zip

[JorgeB]

Start here:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

 

[Verizon]

Hi,

 

thanks for your answer and sorry for the delay, I have already deactivated c-states entirely under amd pbs and my ram is running on stock speeds 2133 mhz, what else could be the problem? Do you see some hints in the logs? Memtest also showed no issues, thought it might be a bad memory module, do you think I should still get the whole ram out and try it with only one stick? And if the issue still occurs try another stick? Thanks in advance for your help!

Edited September 18, 2023 by Verizon

[JorgeB]

17 minutes ago, Verizon said:

Do you see some hints in the logs?

Regular syslog starts over after every reboot, you can enable the syslog server and post that after a crash, in case there's something there.

 

[Verizon]

It’s already enabled, attached you can find the log, whenever it hangs up, I simply reboot it via long press on the power button. Happened again this night, server was offline in the morning.

 

Thank you so much for your help, I really appreciate it!.

syslog-10.10.10.100.log

[Mainfrezzer]

https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

[Verizon]

Done, will give feedback in a few days

[JorgeB]

Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

[Verizon]

Thanks to Mainfrezzer and JorgeB, issue seems to be solved, nonissues since Monday!