January 2, 20233 yr Server and setup is new (set up a week ago). Very slow now opening Docker page, Apps page, any docker. Stopping or starting any docker very slow (5 to 10 minutes). Unraid Web GUI becomes unresponsive for 5 to 10 minutes constantly. Shutdown or reboot command from GUI never completes, hangs. Shutdown or reboot from CLI sometimes works but always takes at least 15 minutes. .............. System Information Model:Custom M/B:ASUSTeK COMPUTER INC. PRIME Z590-A Version Rev 1.xx - s/n: 210890743100313 BIOS:American Megatrends Inc. Version 1007. Dated: 07/08/2021 CPU:11th Gen Intel® Core™ i5-11400 @ 2.60GHz HVM:Enabled IOMMU:Enabled Cache:288 KiB, 192 KiB, 3 MB, 12 MB Memory:16 GiB DDR4 (max. installable capacity 64 GiB) Network:bond0: fault-tolerance (active-backup), mtu 1500 Kernel:Linux 5.19.17-Unraid x86_64 OpenSSL:1.1.1s Uptime: 1 day, 23 hours, 45 minutes. scytale-diagnostics-20230102-0945.zip
January 2, 20233 yr Log is spammed with SMB issues, please reboot and post new diags after array start, first see if docker is still slow.
January 2, 20233 yr Author Waiting for GluetunVPN to update and restart since original post before I reboot. (Might have to abort and reboot anyway) Thanks for the quick reply! ... and Thanks for reminding me to update my profile back soon.
January 2, 20233 yr Author Update: After waiting a long time for GluetunVPN to update and docker page to refresh, GluetunVPN still showed update available. Use GUI to shutdown, then restarted Waited for array to start Docker page far more resposive. Decided to attempt GluetunVPN update again. After about 5 minutes GluetunVPN finally finished update binhex-nzbget and deluge run through the GluetunVPN container ... 10 minutes later binhex-nzbget and deluge rebuilt and things seem to be running. here's a new diagnostics file Thanks! scytale-diagnostics-20230102-1122.zip
January 2, 20233 yr Author Follow up ... ... noticed the Prowlarr docker has disappeared. Tried stopping lidarr ... 2 minutes later "Execution error", hot OK, then screen refreshed automatically and sonar is stopped Tried same with sonarr ... same as above Tried same with radarr ... same as above Tried to restart lidarr ... same as above (but lidarr is started)
January 2, 20233 yr Not clear it should cause problems, but your system share has files on disk1 and cache instead of all on cache. What do you get from command line with this? ls -lah /mnt/cache/system/docker and this? ls -lah /mnt/disk1/system/docker Edited January 2, 20233 yr by trurl fix paths in cli
January 2, 20233 yr Author i must be doing something wrong? root@Scytale:~# ls -lah /mnt/cache/docker /bin/ls: cannot access '/mnt/cache/docker': No such file or directory root@Scytale:~# ls -lah /mnt/disk1/docker /bin/ls: cannot access '/mnt/disk1/docker': No such file or directory root@Scytale:~#
January 2, 20233 yr Author root@Scytale:~# ls -lah /mnt/disk1/system/docker total 20G drwxrwxrwx 2 nobody users 24 Dec 18 17:27 ./ drwxrwxrwx 3 nobody users 20 Dec 18 17:27 ../ -rw-rw-rw- 1 nobody users 20G Jan 2 12:17 docker.img root@Scytale:~# ls -lah /mnt/cache/system/docker total 0 drwxrwxrwx 1 nobody users 0 Dec 18 17:27 ./ drwxrwxrwx 1 nobody users 26 Dec 18 17:27 ../ root@Scytale:~#
January 2, 20233 yr Solution 22 minutes ago, sfleck said: i must be doing something wrong? No I did as you figured out. Corrected my post above. 18 minutes ago, sfleck said: root@Scytale:~# ls -lah /mnt/disk1/system/docker total 20G drwxrwxrwx 2 nobody users 24 Dec 18 17:27 ./ drwxrwxrwx 3 nobody users 20 Dec 18 17:27 ../ -rw-rw-rw- 1 nobody users 20G Jan 2 12:17 docker.img root@Scytale:~# ls -lah /mnt/cache/system/docker total 0 drwxrwxrwx 1 nobody users 0 Dec 18 17:27 ./ drwxrwxrwx 1 nobody users 26 Dec 18 17:27 ../ root@Scytale:~# So your docker.img is on the array. Some good reasons to not have it there. Docker performance will be impacted by slower array, and array disks can't spin down since these files are always open. Not clear those would cause your problems, but might as well recreate docker.img so it will go to cache and maybe a fresh one will work better as well. https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications
January 2, 20233 yr Author oh ... and one last question .... should i set the Default appdata storage location to: /mnt/cache/system/docker/ ?
January 2, 20233 yr Author Docker vDisk location: /mnt/cache/system/docker/docker.img Default appdata storage location: /mnt/user/appdata/ I think this is what you're suggesting
January 2, 20233 yr No, I am not suggesting changing any path or share setting. Did you read the links I gave?
January 2, 20233 yr Author Big thanks to @trurl and @JorgeB for support today. Getting the dockers off disk1 and on to the cache drive is like night and day! I don't know how that get set that way in the first place but it definitely is the wrong approach for a smooth running server. CPU use was running at 100% constantly on at least 6 of 11 cores before ... now 9 / 11 are at 0% Docker containers rebuild in a second and start now just as fast. Everything is back to being zippy.
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.