Edit: I think I meant ngx error, not nginx? I don't know if that is relevant.

 

My Unraid server seems to have crashed overnight. The computer itself was still on and seemed to be running fine, fans all on, hard drives whirring, etc...but no services were accessible, and the monitor couldn't get a signal. I had this same problem a few months ago, I remember doing some research on the log output, didn't really get anywhere and then the problem went away on it's own.

 

I had the setting to mirror syslog to flash on shutdown, but since I had to do a hard reboot I don't think it did that because their aren't any logs on the flash drive from recently.

 

I've set it to mirror all syslogs to flash for now, which I think means if this happens again I'll have some logs to review?

 

Is there anything else I can do to try and troubleshoot?

 

Attached the diagnostics from right after getting it back online, just in case.

tower-diagnostics-20240917-0747.zip

Edited September 17, 20241 yr by aldumil

There's no syslog-previous, don't remember if 6.12.10 already does the auto-rename, see if you have a syslog covering that period on the flash drive logs folder.

42 minutes ago, JorgeB said:

There's no syslog-previous, don't remember if 6.12.10 already does the auto-rename, see if you have a syslog covering that period on the flash drive logs folder.

There isn't I don't think, this is the contents of logs folder on the flash drive: (the syslog.zip has a log for July 18, 2024)

• syslog
• syslog-20240416-092943.txt
• syslog-20240429-123922.txt
• syslog-20240510-130521.txt
• syslog-20240520-074515.txt
• syslog-20240619-191542.txt
• syslog-20240718-135950.txt
• syslog-20240718-162137.txt
• syslog-20240722-135053.txt
• syslog.zip
• tower-diagnostics-20240722-1350.zip
• tower-diagnostics-20240917-0747.zip

check the syslog file, see the period it covers.