From time to time my server is unresponsive. 

Generally restarting nginx through ssh is enough. But today  i couldn't even login with ssh or my kvm. However docker containers were running despite being slow.

Luckily a push on the power triggered a graceful shutdown and the collection of diagnostics attached.

 

The error messages started right after the end of the mover action.

php-fpm[20495]: [WARNING] [pool www] child 927586 exited on signal 9 (SIGKILL) after 15.844115 seconds from start

Not sure about that (with the hour shift) but at the same time i may have had a nextcloud aio backup running (and the mover takes action on the borg backup directory)

 

I don't see in diags obvious reason for that crash. No cpu, memory or storage exhaustion.

Do you see any event that might explain that ?

dionysos-diagnostics-20250402-1133.zip

46 minutes ago, caplam said:

php-fpm[20495]: [WARNING] [pool www] child 927586 exited on signal 9 (SIGKILL) after 15.844115 seconds from start

 

In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM.

 

It could also be one or more containers hogging the CPU, try pinning only some cores to them, and leave cores 0/1 available for Unraid.

 

Also, recommend trying a couple of other things, go to Settings - Global share settings and set the Number of fuse File Descriptors to the max, and enable this:

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down

thanks.

I already created fastusr on flash.

I'll try with the fuse descriptors.

For cpu pinning it will be a journey. I have many dockers running.

I reviewed metrics in monitoring (prometheus node exporter and cadvisor) and nothing obvious. Metrics have been recorded till the reboot with no disruption.