What deployment method did you use to deploy? Docker
Did you follow a particular doc? Which one? No
What issues are you running into upgrading? I didn’t realise the database needed upgrading. I don’t know how to upgrade the database.
I want to revert back to the previous version of rocket chat. So I can retrieve some information. Then I think I’m going to bin the rocket chat server and move to a paid hosted version. This is just too much hassle for someone not familiar with ubuntu.
I’ve tried to go back to the previous version but I get the message:
Can’t find migration version 335
Please help so I can get back online and rectify the situation asap.
Patience and reading is the best way to avoid a mess.
Downgrades:
While Rocket.Chat does not officially support downgrades due to the changes made during database migrations, it is possible to manually roll back migrations separately if necessary.
However if you upgraded say from 7.10 to 7.11/12/13 you may well hit issues.
Method to upgrade is here, but the only guaranteed ‘downgrade’ is via a backup/restore.
Then I think I’m going to bin the rocket chat server and move to a paid hosted version.
Probably a good choice if you are struggling with this.
Thanks for your response. I already tried to upgrade to MongoDB 8.2 using those instructions. I managed to back up the database, but everything after that failed. Couldn’t modify .env (can’t find the file), non of the git statements worked.
If I can’t find a way to upgrade mongodb, what I could really do with is finding a way to get into the old mongodb extract some messages, then I can put the old system to bed and pay someone to host a new one.
I have a backup of the database, but that seems useless? Setting up and hosting rocket chat is one thing, the documentation was all there. I’ve managed to keep it going for years, upgrading and so on. It seems all I need to do is upgrade the database and it’ll work. But, how I achieve this I don’t know? I followed the instructions to set up rocket chat using docker - so surely my db should be easily upgraded following the docker db upgrade documentation, but it’s not. I guess this could be the end of my companies relationship with rocket chat.
If you have a paid pro level then you can of course contact support.
If not it’s open source. YMMV.
Again, this is not a Rocket issue per se.
It’s purely a Mongo thing. Focus on Mongo, not Rocket.
I’d start by clearing out Mongo, import your backup, check it is working, stop Rocket, and then start upgrading Mongo one version at a time. After each version upgrade check Rocket works, rinse & repeat.
This has been asked here multiple times. There are lots of blogs, and Mongo docs too. But no one is going to do it for you.
It isn’t difficult with a bit of knowledge, practice and time. If you are going to admin a server you need to be able to do this - and I’d guess that is why you are still on 5….
Note - I don’t work here. So don’t shoot the messenger.
This is a MONGO issue. Pretend Rocket never existed. How would you go about upgrading Mongo in docker?
It will help if you just tried searching and reading - I have given you multiple references and you just seem to want to ignore them. I do not understand why.
Here’s a clue. Try searching here for this:
FeatureCompatibilityVersion
I can see at least two posts here that will show you how, and that is without even looking on the wider interwebs for help. I do not understand why you haven’t found them yet.
Apart from the change of repo required, the process for upgrading across various versions is pretty well the same.
And no, I am not about to write it out word for word as I don’t use Mongo in docker so can’t be absolutely specific.
What do you think? What does it say about leaping multiple versions? What have I said about leaping multiple versions? Did you not even read my posts?
You have a lot of knowledge I don’t have. I’ve had to guess my way through.
I have read what you’ve written and a whole lot more. I’ve tried various things, I’ve hit google hard, searches like:
mongodb upgrading from 5 to 6 with docker and tried various things, none of it has worked.
Bottom line is, if i’d have got this fixed, i’d have paid rocket chat their $8 a month per employee for a hosted version. But now, i’m just moving to discord instead.
I’ve never known something so fiddly and i’ve been in IT over 30 years. I don’t see why you can’t just install a new database, restore data from backup and point rocket chat at it.
Note that though all this you haven’t really mentioned ANYTHING about your install, your setup, users, licences, and any errors. The only error was when you downgraded, and I told you that you needed to restore first.
That makes it very hard to debug and give proper support.
Nope. I have done a lot of reading. I’ve upgraded Mongo with Rocket several times but only a locally installed version. It is usually pretty painless if you have read and practised a bit. As I said above FeatureCompatibility is the big one. There are plenty of threads all over the place on how to do this.
This is a 10 second search and doesn’t even require Google.
You don’t even have to follow most of it as you are on docker. Shell in, change that setting, stop the DB , change the version in the compose file and start it again. Don’t start Rocket until you are sure the DB is up and OK.. That is about it. 7 to 8 may be more complex (but that is documented here) but should work through 5/6/7 if you are on a small setup.
But you haven’t even told us anything about your setup to actually be able to help you.
Also it won’t work if unless you have the original db restored and you are prepared for a proper upgrade path.
You haven’t mentioned if you had done that.
If you had explained exactly what you had tried to do people may have helped but you hadn’t even got that far.
The trouble is you should have done that before, not after. It’s a wise man that has second thoughts first.
I guess if you took out a Pro subscription and asked them to import it they would help? Seems the obvious solution.
If you have been in IT 30 years you would know that database upgrades are not for the faint hearted. DBs are extremely complex things and there are often big changes between major versions.
Installing a new DB? Have you every tried upgrading say MySQL to Maria DB over 4 versions with docker? Or installing MariaDB 11.x and importing a MySQL 5.x db directly?
You’d also know to follow releases, changelogs, and keep up to date, but you seemed to have ignored all that.
Rocket upgrades have been documented here for years - I know because I wrote some of it myself years back.
The biggest change was around 4-5 when Mongo mandated it was necessary to swap to WiredTiger.
The other was 5+ where Mongo mandated AVX extensions were necessary. You have checked that as well?
Again, we can only guess.
Good luck with Discord. Make sure you keep the db up to date or you’ll end up in the same mess.
