Hi @wgs,
Let’s see if I can help with that.
That looks like some issue with synchronizing the database. I would suggest to run the following script that we have to reset the database info for this rock-on. It will also delete the container if it still exists. This way you can re-install the rock-on using the same shares as before (if you want to re-install it) and you will be in the same state as before/
Briefly, you would need to do the following:
/opt/rockstor/bin/delete-rockon <rock-on_name>
The <rock-on_name>
is case-sensitive, so make sure to verify lower and upper cases. If the container name includes a space, place it inside quote ("Rock-on name with spaces"
).
Then, in the web-UI, refresh the Rock-on page (F5), and then click on the “Update” button in the top right. This will re-fetch all rock-on information and update the database accordingly.
I’m not sure if you mean exactly by “running the update”, but for the Plex rock-on, I believe it should check for update and update itself when the container is started. As a result, turning the rock-on OFF and then back ON should do the trick. The usual procedure to update docker images, however (and rock-on as well), would be to stop the rock-on, uninstall it, click the “Update” button on the rock-on page to refresh all database information, and then re-installing it using the same shares. This would then pull the latest image available.
Let us know how this goes, and I hope this helped!