Docker/Unraid Slow

[Rkpaxam]

Hi All of a sudden my Docker and unraid server have started running really slow, i have checked CPU and ram usage and both are fine. It take 5+ mins to unpack a docker, frequently times out on the web gui.

Starting/stopping contrainers is the same it takes ages and then i get container has already started/stopped or doesn't exist

 

What could cause this? 

Edited March 25, 2023 by Rkpaxam
Missed

[Rkpaxam]

[-MacGyver-]

What you describe in your initial post sounds like network issues. At the very bottom of your screenshot are very slow bond0 inbound/outbound speeds.

 

Have you done an iperf test, both directions, to rule out network issues (  Full disclosure - I haven't used that tool, can't help on setup, operation )

[Rkpaxam]

i have a 500MB connection and have tested no issues with Network. If it helps it started from a powercut last night?

[Rkpaxam]

this is the Main issue, its takign its sweet a** time doing this and i cant access the Nas from any other tab its completely kills it.

 

 

Edited March 25, 2023 by Rkpaxam
Spelling again

[Rkpaxam]

mercia-nas-diagnostics-20230325-1543.zip mercia-nas-syslog-20230325-1544.zip

[-MacGyver-]

You mentioned the unRAID webgui and docker restarts are slow in your initial post. These are internal and your internet connection has no impact on. The iperf test is to test your internal network. Still suggest you test the network.

 

If this was after a power cut restart all of your network equipment. Some part may not have come online properly. With all network equipment turned off, turn back on in the order of modem, router and then any switches. Wait until each has stabilized before continuing to the next.

[Rkpaxam]

Ive Restarted everything today and nothing changed, ive mad sure everything is "moved" im just running a parity check.

Ive done a test on the Cache drive to make sure there are no errors but it is still happening .

 

 

i cant find Iperf but appently its built in? 

[Rkpaxam]

gave up in the end and built the system again must of been a corrupted usb 

[hot22shot]

A little bit too late but you could check that your docker.img file is on your cache and not on your disk.

According to your diagnostic files you had some file(s) from your system share that was/were on your disk2 instead of cache :

 

Quote

system                            shareUseCache="prefer"  # Share exists on cache, disk2