I encountered an odd behavior with one of my Rock-ons resulting in a somewhat “zombie” container: seems apparently frozen, but cannot be stopped, restarted, removed, etc…, from the command line with either
docker tools. Everything else on the machine was running fine and based on a quick Google search seems to happen on non-Rockstor boxes as well (thus suggesting a Docker-related issue).
The fix is easy as rebooting the machine does the trick, but in the meantime, I believe I managed to get the Rockstor database confused with regards to this specific Rock-on. Indeed, in my attempts at stopping the Rock-on, I naturally toggled the Rock-on switch on the web-UI, but since then, this Rock-on remains stuck on the “loading/refreshing” state. This is on the webUI only, as after rebooting the machine everything is running smoothly, including this container.
This problem remains after deleting browser cache or using another machine to connect to the webUI, so this is the reason why I’m suspecting that something is stuck in the Rockstor Rock-on database.
Is there a way to inspect the relevant info in the database and manually fix these, or should I simply use the
delete_rockon() script described below?
Would the latter even fix this problem?
I thought I would ask for feedback before trying the
delete_rockon script, so thanks in advance for any input!