Hi, I have been running Unraid for about a year and a half on a Dell PowerEdge R730, with very few issues so far. Lately, however, the WebUI has become incredibly slow, as in up to 5 minutes to switch from one page to another (eg. Main to Dashboard etc.). There doesn't seem to be any processes eating up CPU cycles or RAM, and everything running on the server (VMs, Containers, etc) are still running just fine, it's just the WebUI itself. I would appreciate any insights as to what's going on, thanks!

Note: The drives in the array are all getting fairly full, but I've been sure to keep at least a couple hundred gigs free on each of them, I don't think that would cause the problem I'm having, but maybe? Anyway, diagnostic logs are attached.

tower-diagnostics-20260307-1431.zip

Maybe not the reason for your question, but some things about your user shares are less than ideal.

Looks like you may have acccidentally created some user shares, some of which no longer exist. You can clean up those non-existing user shares with the CLEAN UP button on the User Shares page.

User Shares are simply the combined top level folders on array and pools.

If you create a user share in the webUI, Unraid creates top level folder(s), named for the share, on array and/or pools, as needed, in conformance with settings you make for the share.

Conversely, if you create a top level folder on array or pools, it is automatically part of a user share named for the folder.

Any user share you don't make settings for has default settings.

Linux is case-sensitive. For example, movies and Movies are different.

You have a lot of shares that seem to have similar names, but they are anonymized in your diagnostics so I can't see them clearly. Possibly you have accidentally created user shares with the same name except for upper/lower case, by specifying a path with different upper/lower case, maybe in your container volume mappings. Many of these have default settings because they were created as top level folders instead of being created as user shares in the webUI. You should spend some time cleaning all that up. Probably, the first step would be to fix all your container volume mappings so they are using a consistent upper/lower case, that way they won't keep creating these problems. Then, combine these shares so there isn't a movies share and also a Movies share, for example, and then check and fix the settings for the shares you end up keeping.

Another thing...

Ideally, Docker/VM related shares - appdata, domains, system - would have all files on cache or other pool with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open.

Your appdata is all on cache, but your domains and system shares are on the array. Arguably, system is the most important share to not have on the array, because these files will always be open if Docker and/or VM Manager is enabled in Settings, even if no containers or VMs are running.

Nothing can move open files. You have to disable Docker and VM Manager in Settings before you can work with these shares.

Simply changing these share to only use cache won't do anything about the files that are already on the array. Those have to be moved.

Something is filling up your syslog with these

Mar  7 04:40:55 Tower kernel: br-2aeb052bdacd: port 1(veth6bc1f00) entered disabled state
Mar  7 04:40:55 Tower kernel: veth6bc1f00 (unregistering): left allmulticast mode
Mar  7 04:40:55 Tower kernel: veth6bc1f00 (unregistering): left promiscuous mode
Mar  7 04:40:55 Tower kernel: br-2aeb052bdacd: port 1(veth6bc1f00) entered disabled state
Mar  7 04:41:53 Tower kernel: br-2aeb052bdacd: port 1(veth7ff68d1) entered blocking state
Mar  7 04:41:53 Tower kernel: br-2aeb052bdacd: port 1(veth7ff68d1) entered disabled state
Mar  7 04:41:53 Tower kernel: veth7ff68d1: entered allmulticast mode
Mar  7 04:41:53 Tower kernel: veth7ff68d1: entered promiscuous mode
Mar  7 04:41:57 Tower kernel: eth0: renamed from veth3f49361
Mar  7 04:41:57 Tower kernel: br-2aeb052bdacd: port 1(veth7ff68d1) entered blocking state
Mar  7 04:41:57 Tower kernel: br-2aeb052bdacd: port 1(veth7ff68d1) entered forwarding state
Mar  7 04:41:59 Tower kernel: br-2aeb052bdacd: port 1(veth7ff68d1) entered disabled state
Mar  7 04:41:59 Tower kernel: veth3f49361: renamed from eth0

constantly about every minute. Don't know what that is about but I don't think it is normal. Maybe that is related to your slowdown.

8 hours ago, trurl said:

constantly about every minute. Don't know what that is about but I don't think it is normal.

This could mean there's a container constantly restarting; check their uptimes to see if you can find out which.

10 hours ago, JorgeB said:

This could mean there's a container constantly restarting; check their uptimes to see if you can find out which.

Yep, that was it! a Docker Compose was constantly restarting, and for whatever reason, it just slowed the whole webui down.