Over the past couple days 2 times I've had my shares become inaccessible and attempting to access the web gui got me a time out issue.  Tried to SSH into the server to no avail.  Never connects.  Doesn't even give me a prompt to log in.  Just blank screen and an eventual connection refused message.

Connecting a monitor and keyboard directly to the server and when I try to login with root it just gives me a message about timing out after 60 seconds and prompts me to login again.

 

So I throw in the towel and quick press the power button on the server which is _supposed_ to clean shutdown.  But on reboot I am notified it was an unclean shutdown and I am now on my second parity check in as many days.  (Ive actually cancelled this second one until I can sort out what is going on)

 

I am attaching diagnostics and the very last part of the logs from the syslog server before it stopped being active.  Any help would be appreciated.

 

Last syslog output before new lines created on the reboot today:

Oct  7 13:01:17 Snuts unassigned.devices: Warning: shell_exec(/bin/lsblk -b -n -o NAME,SIZE,TYPE | /bin/awk '$3 == 'disk' {print $1 ',' $2}' 2</dev/null) took longer than 0s!
Oct  7 13:01:17 Snuts unassigned.devices: Warning: shell_exec(/bin/lsblk -b -n -o NAME,SIZE,TYPE | /bin/awk '$3 == 'disk' {print $1 ',' $2}' 2</dev/null) took longer than 0s!
Oct  7 13:01:17 Snuts unassigned.devices: Warning: shell_exec(/bin/lsblk -b -n -o NAME,SIZE,TYPE | /bin/awk '$3 == 'disk' {print $1 ',' $2}' 2</dev/null) took longer than 0s!
Oct  7 13:01:17 Snuts unassigned.devices: Warning: shell_exec(/bin/lsblk -b -n -o NAME,SIZE,TYPE | /bin/awk '$3 == 'disk' {print $1 ',' $2}' 2</dev/null) took longer than 0s!
Oct  7 13:01:17 Snuts unassigned.devices: Warning: shell_exec(/bin/lsblk -b -n -o NAME,SIZE,TYPE | /bin/awk '$3 == 'disk' {print $1 ',' $2}' 2</dev/null) took longer than 0s!

Last syslog output before new lines created on the reboot from the other day:

Oct  4 05:03:34 Snuts php-fpm[14815]: [WARNING] [pool www] child 2116 exited on signal 9 (SIGKILL) after 408.089840 seconds from start
Oct  4 05:04:42 Snuts php-fpm[14815]: [WARNING] [pool www] child 2194 exited on signal 9 (SIGKILL) after 428.109426 seconds from start
Oct  4 05:05:20 Snuts php-fpm[14815]: [WARNING] [pool www] child 2383 exited on signal 9 (SIGKILL) after 419.205064 seconds from start

 

snuts-diagnostics-20241007-1604.zip

sorry about the typo on the title.  Wish I could edit it to fix to "unavailable"

8 hours ago, DontWorryScro said:

and the very last part of the logs from the syslog server

Nothing relevant there, post the complete syslog, there may be issues logged before the crash.

10 hours ago, JorgeB said:

Nothing relevant there, post the complete syslog, there may be issues logged before the crash.

 

syslog-192.168.100.29.log

Nothing that I can see, 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.