[SOLVED] $ yum update -y breaks rockstor services

[phillxnet (Philip Guyton)]

@exelan Hello again, and you are welcome.

Yes pretty sure this is the known issue of db failure to update from too older version of Rockstor such as you had previously. But the fix I referenced earlier in this thread:

Upgrading to 3.8.16 from 3.8-14 or before? Read this

This guide is for subscribers to Stable updates. Rockstor upgrade from 3.8.15 to the latest release, 3.8.16 is simple. Just click on the update notification in the UI and be on your way. However, some users tend to be on prior versions and may try to upgrade directly to 3.8.16 and this will most likely break. We sent out an e-mail in advance of releasing 3.8.16 to get your system upgraded to 3.8.15 for a smooth transition. But it’s totally understandable some users couldn’t do that in time. This…

requires an interim Rockstor package version of rockstor-3.8.15, which was not available in the testing channel repositories. Hence my previous:

@phillxnet

@suman Is this a Stable channel only version or was it intended to be in Rockstor-Testing repo also? @haoto in the following forum thread seems to have run into the same issue: Upgrading Rockstor from a broken 3.8-14?

As at some point you upgraded from 3.8.14 to 3.8.16 and ran into this very db migration issue.

@phillxnet

But from your reported steps you should not yet be on 3.8.16-2 as the command ‘yum update rockstor-3.8.15’ fails due to no package by that version currently existing in the testing repo. Unfortunately that Rockstor package version is a requirement to avoid a known db issue that breaks Rockstor when it is upgraded from a pre 3.8.15 version as you had to a post 3.8.15 version (hence my embedded note to @suman). But there is still the missing /bin dir!

Again leaving you back at:

@phillxnet

@exelan So for the time being your options are now limited to re-installing. But it might be worth holding out for further information in this thread as if the 3.8.15 package appears in the Testing repo soon then you can continue on from here with the linked instructions.

As from my VM here to replicate your issue (bar the missing bin) we see that 3.8.15 is not available in testing updates channel repo still:

yum clean all
yum list available rockstor --showduplicates
Loaded plugins: changelog, fastestmirror
Loading mirror speeds from cached hostfile
 * base: repo.uk.bigstepcloud.com
 * epel: www.mirrorservice.org
 * extras: repo.uk.bigstepcloud.com
 * updates: repo.uk.bigstepcloud.com
Available Packages
rockstor.x86_64                                           3.8-12                                             rockstor        
rockstor.x86_64                                           3.8.16-1                                           Rockstor-Testing
rockstor.x86_64                                           3.8.16-2                                           Rockstor-Testing
rockstor.x86_64                                           3.8.16-4                                           Rockstor-Testing
rockstor.x86_64                                           3.8.16-5                                           Rockstor-Testing
rockstor.x86_64                                           3.8.16-6                                           Rockstor-Testing

The changes in db management between 3.8.14 to 3.8.16 were fairly major, hence the inadvertent breakage in testing channel updates. You may well still be required to reinstall using the latest iso given the missing (possibly impractical to add) specific interim package versions for testing. Heeding the tips / warning we covered earlier in this post.

I know this is frustrating but I hope you can persevere as your input here has already been very valuable:

I particularly like you reverse proxy / lets encrypt post:

Getting nginx to work remotely and securely via HTTPS/SSL

Hi there, I’ve done a ridiculous amount of searching and IRC bothering on getting a lot of the Rock-On containers to work with nginx via reverse proxy all passed through SSL/HTTPS. I finally got a great set up working so I wanted to share with the rest of the world considering I found absolutely no configuration online as to what I wanted. This how-to is a work in progress, so please feel free to send me a message or comment on this page if there are any suggestions or if I’m blatantly providin…

But the testing channel updates are rather bleeding edge and need to be if we are to realise more of what we are aiming at.

Hope that helps.