This goes on for ever, and across reboots. Note that the Rock-On service switch on the left is replicating itself. If I hit update I’m sent to the All categori. Turning the Rock-On service off and then on doesn’t help either.
I have tried stopping plex through the command line “Docker stop Plex”, and starting it again “Docker start Plex” the commands do not error out, I just get the answer “Plex”.
But Plex is definately not working.
I think the error came when I turned the Plex Rock-On of, and then turned Rock-On itself off, before the interface showed that Plex was stopped. Perhaps something went wrong.
Absolutely. There’s no need to re-install…yet My motivation here is to understand the buggy behavior better and improve the code as needed. I do have a simple fix for you, but we are both on the same page to debug it a bit more. Could you please send me the log files in /opt/rockstor/var/log directory?
You may know this already, but you can zip the files with this command: tar czf log.tgz /opt/rockstor/var/log.
Thanks @KarstenV for the logs. I am glad we solved the problem, thanks for playing. Let me summarize the issue.
The rockstor service has a child service called ztask-manager which handles asynchronous jobs. for example, long running tasks like Rock-on installations etc… including starting and stopping. It is pretty fault tolerant and retries failed tasks. When @KarstenV turned off Plex and immediately the Rock-on service, the plex job failed because it cannot be turned off without Rock-on service. The ztask-manager tried a few times and gave up. And the UI kept spinning because the Plex Rock-on is still in “pending_stop” state. ztask-manager will only try again if it’s restarted. So the solution was to start the Rock-on service and then restart rockstor from the terminal (systemctl restart rockstor) which restarts ztask-manager, which then tries to stop Plex again and it succeeds this time because Rock-on service is indeed running and can process the stop request.