I’m running unraid on an old laptop with i5-1135G7, 8 gb ram. Whenever the server crash it shows this in the logs (pic attached), also, when I press power button the shutdown process gets stuck on the stopping unraid api step.

The server is connected via wifi, docker custom network type is macvlan.

Edited March 5Mar 5 by Aman Saroha

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

These are from previous crash.

tower-diagnostics-20260303-1009.zip syslog syslog-previous

Mar 3 09:16:51 Tower php-fpm[5272]: [WARNING] [pool www] child 1237718 exited on signal 9 (SIGKILL) after 93.951809 seconds from start

Mar 3 09:17:35 Tower php-fpm[5272]: [WARNING] [pool www] child 1237730 exited on signal 9 (SIGKILL) after 97.313165 seconds from start

Mar 3 09:18:15 Tower php-fpm[5272]: [WARNING] [pool www] child 1237739 exited on signal 9 (SIGKILL) after 101.398115 seconds from start

Mar 3 09:18:54 Tower php-fpm[5272]: [WARNING] [pool www] child 1237745 exited on signal 9 (SIGKILL) after 89.952548 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