Hi team. I've updated to 7.1.4 at the same time that my USB drive failed and I replaced it using the guidance on UnRAID documentation. After starting using this version, I started to see that, some hours after a reboot, this lines in the syslog file:

Jun 24 07:36:43 unraid php-fpm[2800523]: [WARNING] [pool www] server reached max_children setting (80), consider raising it

As you can see, I already raised the max_children value using the /boot/config/go file to change this value from /etc/php-fpm.d/www.conf to no avail.

After further review I see that my process list, at the time the service hangs and before I restart it, is flooded with du -sb commands. Using htop, I can see it is related with php-fpm as you can confirm in the screenshot below:

If I restart the service, the web portal is restored for some hours and then breaks again. But the list of pending processes are not cleaned up anytime I restart the service. Dozen and dozen of services continue to be listed and my Load Average goes to the roof. I need to use htop to manually kill each process to get load average low and keep system integrity.

I haven't determined yet the root cause, but it seems that the command is used in UnRAID to calculate folder size, which I'm not using at all by issuing that command in the web service. Also, it seems the service is executed, and it hangs there without closing.

Attached you find my diagnostics file for you review and looking forward to get your time and expertise to identify the root cause and place suggested corrections to avoid it in the future.

unraid-diagnostics-20250624-1713.zip

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

RAM is not the root cause, at least directly. I detected I had a oom-kill related with qemu and the unique virtual machine that I have with 8GB of RAM and without balooning. Now, with it started, I have this RAM consumption:

Another thing I detect is a discrepancy between CPU comsumption graphin in UnRAID comprated with htop. htop gives me 5-10% per core when the UnRAID graphic gives me 80-90% constantly. I'm unable to detect any docker container with such high usage, as all containers have 0-1% CPU usage.

The system is not unresponsive when the service is up, or I see slowness on it. Only the high load average that grow along the time due to multiple du -sb hanged commands make the system slower until service hangs. If I kill the PID for those, load average reduced to normal values.

I assume the root cause is other.