February 22, 20233 yr When trying to update a specific docker config, I was presented with an error about failing to stop the docker, and thus failing to start up the container with the new config. I tried to stop and then kill this container via cli (docker kill <containername> ) which also failed ( cannot stop container: <container-id>: tried to kill container, but did not receive an exit event ). I tried to stop the docker engine via the webinterface - which seemed to succeed, but upon starting it again docker daemon was unresponsive. I then tried to reboot from the webinterface - which send a message to all ssh connections, but didn't seem to do anything else. I tried again with shutdown (repeatedly) and in the end with shutting down the array manually. But this also failed and stayed forever (~20h+) on "Stopping Array - stopping services" (or similar) status. I'll add diagnostics from the point but as far as I can see there is nothing out of the ordinary in the syslogs. In the end I resorted to a hard reset, lacking other options. After this hard reset and starting docker, the container (Cloudflare DDNS) reacts without issues, so I still suspect some other system service being the hidden cause. This might be related to the linked issue below, but if it is then the thread also did not reach to the point of identifying the failing service. unraid-diagnostics-20230221-2135.zip
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.