Been a while since I last had a problem so here goes.   Recently the server started becoming non responsive to connecting to the GUI but all the dockers kept working for at least a couple hours.  After that even the dockers stop working and I can't connect to anything.  Here's the diagnostics and i'll be on all day to try and figure this out.  Only thing I changed recently was having to redo my network for a move but I simply gave it the same static IP address as before and set it up in unraid to have that IP address.   Only weird thing I'm running on that end is that its in a link aggregation.  

Thank you ahead of time. 

Diag.zip

Diags after to be after a reboot, enable the syslog server and post that after it happens again.

just happened again and i had the syslog on for a bit before that.  should have posted that as well.  Sorry

syslog-Waz-Server.log

There appears to be a container constantly restarting, look at their uptimes, so see if you find out which.

That would probably be Pelican-Wings.  That should be unrelated to this as I just started messing with that today/yesterday.  Its giving me trouble so and Im messing with its config file so I have to restart it every time i make a change. 

Fix that and post a new syslog if it still crashes.

I'm back sorry it took so long.  Got that docker taken care of and let it run for a few days.  Still crashing roughly every 24 hours.  

waz-server-diagnostics-20250513-2030.zip

And here's the syslogs.

 

I also updated to 7.1.2 hoping that would help.

 

 

syslog-Waz-Server.log

Unfortunately, there's nothing relevant logged, this can also 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, including the individual docker containers. 

I was afraid of that.  Is there any indication of whether it's the flash drive failing? 

 

Even still Im about to pick up a Samsung FIT 64gb (they don't make any smaller anymore) and run it on the internal 3.1 usb port and see if that helps. 

 

Thanks as always I appreciate it. 

 

 

20 minutes ago, TheIlluminate said:

internal 3.1 usb

USB2 is more reliable for the boot flash and speed isn't important.

4 minutes ago, trurl said:

USB2 is more reliable for the boot flash and speed isn't important.

ive seen the reason being heat and that shouldnt be concerned for this on as the usb 3.1 internal spot on a r360 is right in front of the pcie slots so it gets PLENTY of airflow.  

on a side note samsung doesn't even sell usb 2.0 drives anymore and the usb 2.0 slot on the server is technically for idrac access.  I "could" plug it in there but i would like to put it on the internal slot if i can.  

appreciate the response im just looking for more information on why 3.x seems to fail more often.