Hit the upgrade button and now sabnzbd is not in list - but still running!?

[Flox]

Hi @baretomas, and welcome!

I’m sorry to read you’re having issues, but I’ll try to help.
First of all, I suppose that by “upgrade button” you mean the “update button” so I will assume this from now on. Please correct me if I’m wrong.

Let’s try first to fix the problem and I’ll then provide some information on what happened and the error you received. The fact that Sabnzbd is still working fine does mean, indeed, that the problem only lies with getting it back to the displayed list of rock-ons.

@baretomas

Maybe its best to use the “delete” script mentioned here on the forum, and reinstall it?

This will indeed work, but let’s try to see if we can try something much simpler first. You most likely already tried what I’m going to list, but it’s worth asking and/or trying just in case as it would save you the rock-on reinstall.

1. Refresh the page (Ctrl + Shift + R in Chrome). Indeed, Rockstor updates the status of all rock-ons when loading this page so this may refresh whatever status is in limbo.
2. Click the Update button. Similar to above, this will trigger Rockstor to fetch the list of rock-ons available from the server and update the local information accordingly. See below if you see an error as you did in your original post.

If neither one of these work, then yes, I would go ahead and try running the delete script. As a reminder, you can see in the post linked below for more details. In the case of Sabnzbd, you would need to run the following command:

/opt/rockstor/bin/delete-rockon sabnzb

Rock-on stuck in "loading" state

@Flox Hello again. I think what you are looking for is: /opt/rockstor/bin/delete-rockon Delete metadata, containers and images of a Rock-on Usage: /opt/rockstor/bin/delete-rockon <rockon name> ie an installed (built) system has the above convenience wrapper that sets up the required environment for the script. And with no parameters give it outputs the above ‘guide’ as to it’s use. Hope that helps. You may have to play with getting the exact Rock-on name but pretty sure it’s the displayed…

As you probably already saw, this script will wipe all reference to this rock-on in Rockstor’s database, so pressing the Update button afterwards should reset its status to “available” and you will be able to install it again. Using the same shares as before will allow you to get back in the same state/config as you were before.

Now, let’s talk about the error you saw, what happened, and why.
I assume you saw an error similar to below:

Error while processing remote metastore at http://rockstor.com/rockons/root.json. Lower level exception: HTTPConnectionPool(host=‘rockstor.com’, port=80): Max retries exceeded with url: /rockons/root.json (Caused by <class ‘socket.error’>: [Errno 11] Resource temporarily unavailable)

You message was most likely slightly different and mentioned Plex, but is essentially caused by the same thing: a simple web timeout. This means that trying again usually works. As it reads the configuration of each rock-on one after the other, it will report an error for whichever rock-on was being processed when the timeout occurred (Plex in your case). Although this isn’t a big deal per se as trying again usually works, it seems to have conflicted with checking for and updating the status of your installed sabnzbd rock-on. I’m unsure how that happened exactly, unfortunately, but I have a couple of ideas on a few improvements we might be able to add in order to ensure that what Rockstor displays is in sync with what is running on the machine, for instance. It may be a little while until I can try to seriously look at that, however, but I’m hopeful this will get improved and be more robust in the future.

Overall, give a try to the reload (1) and update button (2) options first, and if no change, then go ahead with the delete-rockon script. That should fix it, but let us know how it goes!

Hope this helps,