Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Server frequently becomes very slow/not responding after upgrading to 7.0.1

Featured Replies

After upgrading to 7.0.1 from 6.12.something, I noticed that the server has become unresponsive frequently.

Server log shows multiple lines like

I think the WebUI as well as SSH connection become sluggish as soon as a Docker container starts doing some data reading/writing, though I can't say for sure if that's the cause or only a symptom.

I tried searching around a bit but didn't find anything conclusive about this problem.

There are suggestions to install more memory or checking rootfs size, but I don't think they apply since neither of those are close to being full on my server.

I have attached the diagnostics that I got during such a slow down.

Thank you in advance for any advice.

tower-diagnostics-20250306-2259.zip

Solved by JorgeB

  • Community Expert
  • Solution
Mar  6 23:04:48 Tower php-fpm[10693]: [WARNING] [pool www] child 721047 exited on signal 9 (SIGKILL) after 69.962349 seconds from start
Mar  6 23:04:52 Tower php-fpm[10693]: [WARNING] [pool www] child 721118 exited on signal 9 (SIGKILL) after 57.157382 seconds from start
Mar  6 23:05:05 Tower php-fpm[10693]: [WARNING] [pool www] child 716316 exited on signal 9 (SIGKILL) after 395.223758 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

  • Author
2 hours ago, JorgeB said:

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

Thank you JorgeB, I will first try these and see how it goes.

If things still don't improve I will then try the CPU pinning, though that might be a bit awkward since the CPU I'm using only has 4 cores and no Hyperthreading (i3-8100), so there is not much room to play with.

  • Author

This morning I checked the server log and found that the php errors were still being produced,

Quote

Mar 7 08:11:15 Tower php-fpm[10647]: [WARNING] [pool www] child 2018117 exited on signal 9 (SIGKILL) after 12.161461 seconds from start

Mar 7 08:12:12 Tower php-fpm[10647]: [WARNING] [pool www] child 1983697 exited on signal 9 (SIGKILL) after 501.304185 seconds from start

Mar 7 08:16:05 Tower php-fpm[10647]: [WARNING] [pool www] child 2018737 exited on signal 9 (SIGKILL) after 290.397098 seconds from start

however, there were also these lines:

Quote

Mar 7 08:46:16 Tower nginx: 2025/03/07 08:46:16 [error] 13776#13776: *234457 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 52.46.94.4, server: , request: "GET /plugins/dwmemtester/include/dwmemtester_status.php?getfs=no HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "52.46.94.2", referrer: "https://52.46.94.2/Plugins"

Mar 7 08:46:26 Tower nginx: 2025/03/07 08:46:26 [error] 13776#13776: *234457 FastCGI sent in stderr: "Unable to open primary script: /usr/local/emhttp/plugins/dwmemtester/include/dwmemtester_status.php (No such file or directory)" while reading response header from upstream, client: 52.46.94.4, server: , request: "GET /plugins/dwmemtester/include/dwmemtester_status.php?getfs=no HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "52.46.94.2", referrer: "https://52.46.94.2/Plugins"

Mar 7 08:46:36 Tower nginx: 2025/03/07 08:46:36 [error] 13776#13776: *234457 FastCGI sent in stderr: "Unable to open primary script: /usr/local/emhttp/plugins/dwmemtester/include/dwmemtester_status.php (No such file or directory)" while reading response header from upstream, client: 52.46.94.4, server: , request: "GET /plugins/dwmemtester/include/dwmemtester_status.php?getfs=no HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "52.46.94.2", referrer: "https://52.46.94.2/Plugins"

 

As such, I went and removed that Memory Tester plugin, as well as a few other that I don't use anymore.

After checking back in the afternoon, the system log seems to be clear of errors and the Web UI seems snappy as it should be, so I think that plugin might have been it.

  • Community Expert

Doesn't seem very likely to me the plugin was the issue, but let us know if you find anything else.

  • Author

Yeah you are probably right. I was too quick to come to that conclusion as Web UI was still locking up. I tried a few other things but finally gave up and setup CPU pinning so the Docker containers only use cores 1-3 and core 0 only for Unraid. It seems to work for now.

 

I wonder why that's necessary now on 7.0.1 though, 6.12.11 was running without a hitch.

  • Author

I have downgraded to 6.12.11 and the server is running smoothly again.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.