Trying to update Rock-ons error

[Please complete the below template with details of the problem reported on your Web-UI. Be as detailed as possible. Community members, including developers, shall try and help. Thanks for your time in reporting this issue! We recommend purchasing commercial support for expedited support directly from the developers.]

Brief description of the problem

Trying to update Rock-ons , specically Plex server and I get this error]

Detailed step by step instructions to reproduce the problem

[write here]

Web-UI screenshot

[ Traceback (most recent call last):
File “/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py”, line 41, in _handle_exception
yield
File “/opt/rockstor/src/rockstor/storageadmin/views/rockon.py”, line 429, in _get_available
response = requests.get(remote_root, timeout=10)
File “/opt/rockstor/eggs/requests-1.1.0-py2.7.egg/requests/api.py”, line 55, in get
return request(‘get’, url, **kwargs)
File “/opt/rockstor/eggs/requests-1.1.0-py2.7.egg/requests/api.py”, line 44, in request
return session.request(method=method, url=url, **kwargs)
File “/opt/rockstor/eggs/requests-1.1.0-py2.7.egg/requests/sessions.py”, line 289, in request
history = [r for r in gen] if allow_redirects else []
File “/opt/rockstor/eggs/requests-1.1.0-py2.7.egg/requests/sessions.py”, line 133, in resolve_redirects
proxies=proxies
File “/opt/rockstor/eggs/requests-1.1.0-py2.7.egg/requests/sessions.py”, line 279, in request
resp = self.send(prep, stream=stream, timeout=timeout, verify=verify, cert=cert, proxies=proxies)
File “/opt/rockstor/eggs/requests-1.1.0-py2.7.egg/requests/sessions.py”, line 374, in send
r = adapter.send(request, **kwargs)
File “/opt/rockstor/eggs/requests-1.1.0-py2.7.egg/requests/adapters.py”, line 213, in send
raise SSLError(e)
SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)

Drag and drop the image here]

Error Traceback provided on the Web-UI

[paste here]

@deigo Welcome to the Rockstor community.

Is this a Rockstor v3 variant. That now has a rather old CentOS base and we no longer release updates for it. Plus there is a known ssl issue that may well be causing your:

In short this is down to out-of-date SSL certs in our CentOS base used in v3 Rockstor.

@Flox has a nice explanation and work around here:

However you would be far better off re-installing our v4 “Built on openSUSE” as that is what we are now working on. It’s also very nearly at stable status (Release Candidate 10), and pre-build installer can be downloaded from our website:

https://rockstor.com/dls.html

Take a look at our v4 installer how-to here: https://rockstor.com/docs/installation/installer-howto.html

Hope that helps.

1 Like

Thanks for your reply, I have been looking into installing v4. I do subscribe ton stable updated will that still work when reinstalling?

Yes. But if your existing Appliance ID in Appman is upper case you will have to edit it to lower case.

https://appman.rockstor.com/

Early versions of our CentOS base, due to earlier kernels, produced lowercase Appliance ID’s. Later versions of our CentOS variant and very early version of our v4 “Built on openSUSE” had uppercase Appliance ID’s. Basically the kernel reverted to correct behaviour in producing lower case uuid’s which we then use verbatim for our Appliance ID. So all current v4 Rockstor versions have lowercase Appliance ID’s.

Also on some motherboards the uuid generated is non unique and so we have to generate a random one, it’s used for things like replication as well so they must be unique. Likewise you just edit your subscription’s Appliance ID within Appman and the activation code will be immediately associated with the edited version of the Appliance ID instead.

Another caveat is that we aren’t yet at the first v4 stable and so we have an empty Leap 15.3 (current) repository. That’s more of a cosmetic issue as zypper ignores such repositories but you will see errors to this effect in the logs. However upon us reaching our first v4 stable rpm release this will be resolved. We have a place holder rpm of v4.0.4-0 in our 15.2 base repository but that was to address an issue we have now resolved regarding repository setup. Both repositories should be updated soon when we have our next v4 release. We are now working on the last issues before that release.

Hope that helps.

3 Likes