Hello.

 

I'm wondering if someone could help me.

I'm experising slow GUI on my unraid server. After a fresh reboot the server respons perfectly but after a while (maybe 10-20 minuter) the server becomes more and more unresponsive, to the degree that it takes about 30-60 minutes to navigate within the GUI.

Dockers work perfectly, so no issues there. I've had this issue for a couple of month now and tried some troubleshooting.

I've changed the sata cables for the cache drives and also tried different sata ports on the motherboard.

Turning off all the dockers don't help, but disabling the docker function does. If docker is disabled the server is as after a fresh reboot.

If I turn tocker back on it starts to get more and more slow again.

 

I've looked in the syslogs and don't understand much of it, but I've seen some "out of memory" posts, but I don't see the RAM meter on the dashboard reach anywhere near 100 %.

I have a few dockers like plex, radarr, sonarr, lidarr, nextcloud and so on. I have 24 GB of ddr4 ram and have had the server for a couple of years now, but the issue started about two month ago. So I'm thinking if it really is a RAM issue, because shouldn't the issue have started right away then?

 

I don't want to buy more RAM just for troubleshooting and that wasn't the solution, you know.

 

So, could someone please help me try to figure out what the cause of the issue might be?

 

Thanks!

tor-syslog-20200609-0753.zip

Edited June 9, 20206 yr by LordShaaver

After reading your description, I suspect that you may have set one of your Dockers setup wrong.  Check to see that if any 'catalogs' (think-- media catalogs) of stored data are actually being stored on the RAM disk that Unraid uses for its operating system.  These should be saved on the array,   To isolate which one is causing the problem, you may have stop one (at a time) from starting until you find the offender.  (Please note:  I do not use any of the Dockers that you mention but there are support threads for each of them. Once you find the problem one, you can ask questions there...)

Edited June 9, 20206 yr by Frank1940

With your help I now found that it isn't a specific docker container that's causing this. It is when a combination of certain containers is running that the problem manifests itself.

A bit odd but now I know where to look and try to find out what they have in common.

 

Thank you for taking time and helping me!!

 

 

Update:

It turns out it was an M.2 harddrive mounted through unassigned devices that was the root cause. As soon as I unmount that drive the GUI started responding again. When I had that drive mounted and in use by certain docker containers the GUI began to be unresponsive.

Edited June 9, 20206 yr by LordShaaver

43 minutes ago, LordShaaver said:

It turns out it was an M.2 harddrive mounted through unassigned devices that was the root cause. As soon as I unmount that drive the GUI started responding again. When I had that drive mounted and in use by certain docker containers the GUI began to be unresponsive.

I seem to recall (a bit vaguely) that if Unassigned Devices mounts a drive that is not physically present (or available) on a system, it will create that drive on the Unraid RAM disk.  That would certainly fit the description of what you were/are seeing.  (Again, recalling, usually it is a USB drive that has been physically disconnected.)