After several years of reliable service and a recent upgrade of Unraid OS my server times out after a few hours and you can't connect.  The only way to bring it back online is to reboot the server.   I changed DNS setting to a local server to 8.8.8.8 and 1.1.1.1 but that didn't work.  I have included the sys log in this topic.  Please advise.

 

 

sys log.txt

Enable the syslog server and post that after a crash together with fresh diagnostics.

Okay, will post again after using these tools.

It crashed again after overnight and would connect in browser (timed out).  Please see the updated files attached.

sys log Nov_23_23.txt melvinsvr-diagnostics-20231123-0952.zip

The syslog you posted only covers two minutes of uptime.

 You have to reboot in order to login with a browser to retrieve the log.  Apparently the log starts over when you reboot.  Is there a way to retrieve an older syslog file?

20 minutes ago, tcm2Lions said:

Is there a way to retrieve an older syslog file?

did you enable the syslog server as mentioned earlier to get a persistent syslog.

Yes, I enabled Local syslog server in settings.

22 minutes ago, tcm2Lions said:

Yes, I enabled Local syslog server in settings.

Then there will be a log in wherever you told it to store logs if you set the server to log to itself, or the 'logs' folder on the flash drive if you used the mirror to flash option.

Okay, it was set to appdatabackup. just need to find it.

Having trouble finding the Syslog file.  I checked the settings... is the file "CA_backup.tar"?

Nope, enable the mirror to flash drive option in the syslog server and then get it from the flash drive /logs folder.

Please see the attached files.

melvinsvr-diagnostics-20231129-0905.zip syslog

Unfortunately there's nothing relevant logged, 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.

Does the log say that it actually crashed and refused to connect?  When it doesn't allow you to log on in the browser the server is still running.  I'm trying to determine if it is a network issue of my local network.

I missed before that you have the S3 plugin installed, the server may be going to sleep and not waking up, try removing it.

ok, I will try that.

Okay, that seems to have worked.  I can log in with the browser the next day and it did not time out. Thanks.