Unraid: 7.2.3

My server freezes every night and I am not able to access the GUI for anything running on the server. Not the unraid dashboard or even my arrs. Everything still seems to run in the background but I cannot access the GUI. In order to get back in I have to force shutdown the server and start it back up.

I thought my issue was because of new dockers that I installed and then messed up. So i disabled them and waited. That didnt work

I read somewhere to pin all dockers at CPU 3+ to leave unraid the resources on bottom ones.

Ive looked at lot of different web searches to find out what is going on and nothing is working.

Note that I did upgrade to 7.2.3 from i think 7.0.2. But i did not have these issues until i updated. Everything worked great.

unraid-diagnostics-20260205-1244.zip syslog-192.168.1.115.log

Feb 6 05:37:41 Unraid php-fpm[5959]: [WARNING] [pool www] child 837697 exited on signal 9 (SIGKILL) after 13.180498 seconds from start

Feb 6 05:37:53 Unraid php-fpm[5959]: [WARNING] [pool www] child 837720 exited on signal 9 (SIGKILL) after 12.148043 seconds from start

Feb 6 05:38:05 Unraid php-fpm[5959]: [WARNING] [pool www] child 837737 exited on signal 9 (SIGKILL) after 12.347878 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. Ill try testing with pinning specific dockers to cores and see who is causing the problem. I did leave 0/1 for unraid specifically but even with that I was not able to access the GUI.

Forgot to mention, someone having a similar issue recently mentioned that changing the Docker paths to a disk path helped a lot, so it may also be worth a try. If you were using a pool you could use an exclusive share, but not with the array. Also note that because of parity, having system in the array is not ideal, an SSD pool would be much better.

Still, you can try changing both the Docker image and appdata (but the latter currently it exists on disk1 and 2, so it would need to be consolidated fisrt), e.g.:

Instead of /mnt/user/system/docker.img it would be /mnt/disk1/sytem/docker.img

Same for appdata once it exists on only one disk.

So an update on this issue. I dont think it fully fixed itself as what i did was little hacky. But this night i didnt have the issue this time.

In the Extra Parameters: (in advanced view) for each tdarr and plex containers. I added the value --memory=2G (for tdarr and 6gm for plex).

This seems to helped fix the issue for now.

This is in addition to the one link you provided

Excessive flash drive activity slows the system down

If the system is running slowly, check the Main page and see if it shows significant continuous reads from the flash drive during normal operation. If so, the system may be experiencing sufficient memory pressure to push the OS out of RAM and cause it to be re-read from the flash drive. From the web terminal type:

touch /boot/config/fastusr

and then reboot. This will use around 500 MB of RAM to ensure the OS files always stay in memory. Please let us know if this helps.