Hi everyone,

For a few days now, my docker service has been very slow and no longer responds correctly. Impossible to delete containers / impossible to restart them.
I've also tried to stop docker, but the Unraid loading bar keeps running. Ditto on the server restart attempt.

I've attached the diagnostic.

Do you have any ideas?

Thx

groot-server-diagnostics-20250424-0948.zip

Logs are full of SSH spam, reboot and post new diags after array start.

@JorgeB here, the new diagnsotic after a restart.

groot-server-diagnostics-20250424-1348.zip

Edited April 24, 20251 yr by tubleuf

Everything seems to work fine after the reboot. Is it possible to reduce the verbosity of ssh logs?

Not that I'm aware of, is all that SSH activity expected?

I don't know why there's so much SSH activity. I've just shut down the service as it's not necessary at the moment. I wonder if it isn't the Tailscale SSH service...

I don't think that's normal with Tailscale.

New day, new (same) problem. Docker is down again: very slow and impossible to delete a container without error -> "execution error".

I add that is not possible to stop the array: stopping service still in progress...

You can find a new diagnostic in attachment. Do you have some ideas on this problem ? 

groot-server-diagnostics-20250425-0957.zip

Edited April 25, 20251 yr by tubleuf

Docker folder is being stored on disk5, that is not recommended, it should exist on an SSD based pool, would also recommend using an image instead of a folder, since these have been known to sometimes cause strange issues.

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Then:
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

Thank you. @JorgeB for your feedback.
Do you mean that the docker image should be on a cache pool or just an SSD pool? Today I have this disk structure (see screenshot) -> what is your recommendation? 

5 minutes ago, tubleuf said:

Do you mean that the docker image should be on a cache pool or just an SSD pool

Any pool will do. 

 

SSD based will give better performance that a HD based one but both are better than in the main array.   

 

With your drives the 'cache' pool looks sensible but you are free to add another pool for that purpose if you want..

To adapt my setup according to the recommandation, I tried to :

• start Unraid without starting Docker or VM services
• moove “share” with the Unbalanced plugin 

I notice that Unbalanced plugin stops the test process during the plan step without any further details. So I forced the plugin to stop.

The Array can't be stopped because Unraid can't unmount this disk:  Array Stopping•Retry unmounting disk share(s)...
 

Apr 25 17:24:03 groot-server root: umount: /mnt/disk5: target is busy.
Apr 25 17:24:03 groot-server emhttpd: shcmd (151): exit status: 32
Apr 25 17:24:03 groot-server emhttpd: Retry unmounting disk share(s)...

 

I checked the file system status of the disk5 : passed.

 

I don't underdstand the problem... 

 

New diagnostic in attachment. 

groot-server-diagnostics-20250425-1720.zip

Edited April 25, 20251 yr by tubleuf

That means something is still using the disk, and also one of the typical issues that docker folders can cause, type reboot in the CLI, then disable docker and VM services and only re-enable after you recreate the image

Update: I have changed the docker folder for an image and changed my SSD in a pool. For the moment everything works fine.
 hope that all will be okay 🤞
Thx @JorgeB and @itimpi