Hi,
I just updated to RC 8.0.1 and had to upgrade my Mongodb. I am running Mongdb 8.0.18 and RC 8.0.1 In the workspace under deployment RC shows Mongodb 6.0.19 / wiredTiger (oplog Enabled)
Is that correct? I do not have any instance of MongoDB 6.0.19 running anymore. Do I need to migrate the Database ?
You make no mention of your setup at all so makes diagnosis difficult.
Always read the release notes BEFORE you upgrade. Save yourself a lot of hassle and heartbreak.
I presume you are not running Mongo in docker? If you are you should be reading this.
If not then check the rocketlogs at startup, It should tell you which Mongo version it detects.
Have a read here and provide the informaton required.
Sorry for being a bit short with my explanation. I do run Rocketchat and MongoDB in Docker containers. I run the latest official Rocketchat image and the official mongdb 8.0 Image (not the Bitnami Image) I run 2 mongoDb instances in a replica set.
After I upgrade both, Rocketchat AND the mongodb replica set, everything works just fine! I do not have an issue. The log shows that the MongoDB version 8.0.18 is detected.
------------------------------------------------+
| SERVER RUNNING |
+-------------------------------------------------+
| |
| Rocket.Chat Version: 8.0.1 |
| NodeJS Version: 22.16.0 - x64 |
| MongoDB Version: 8.0.18 |
| MongoDB Engine: wiredTiger |
| Platform: linux
However, in Rocketchat under workspaces in the admin panel it shows this one:
Database Migration
318 (December 21, 2025 12:02 PM)
MongoDB
6.0.19 / wiredTiger (oplog Enabled)
I was wondering if I need to do something in Rocketchat to let Rocketchat know that the Mongodb is now on Version 8 feature set.
Which licence type do you have & number of users?
I have to check when I’m Beach at work, but what has the license and user to do with my original question?
I just want to know what I see is normal or if it requires any more attention.
If you knew the answers you wouldn’t be asking here would you?
I ask for a specific reason. Also why I asked about history.
I don’t work on guesswork. Just facts.
As you are the one with issue, not me, you probably ought to answer those who may have a solution. Without that you become this.
See “what to do about it”.
I’m sorry, your answer is 0 helpful. I don’t ask for advice how to fix an issue. I don’t know if I have an issue! I’m not attempting to do Y to for a fix which needs X. If I have an issue, I’ll do the proper things to fix it. But again, right now, I don’t even know if I have an issue.
RC boot logs detect the right Mongdb Version, but in the workspace I see a different version. Is this normal or not? Everything else is just fine. If this is not normal, I’ll try to fix it myself,but I can’t find anything in the documentation which tells me if this is normal or not. This doesn’t mean it’s not in the documentation, I just couldn’t find it, if it is.
My answer is 100% accurate. You just don’t like it because it doesn’t give you an answer, and that is because I can’t becuase I don;t have enough information.
As I said - I think I might know why you have the issue, and it may well be genuine, but you clearly don’t.
However, as you haven’t provided the information I have asked for I can’t tell for certain so I am not going to randomly guess and give you wrong advice. I don’t work that way.
Remember, I don’t work here. Just a volunteer helper so don’t shoot the messenger.
My guess is you are on CE with a lot of users and probably upgraded from an older version, and that will explain the issue. But as you haven’t told us the whole setup as you were asked I am not going to hazard a guess at the problem and a fix.
If I’m right then good luck - I hope you have backups. You may well need them soon.
Awesome, according to your message it’s not correct what I see.
I’ll check into it.
I run backups every 4h, happy to use one if I need to.
I didn’t say exactly that.
You assume far too much. Facts matter.
No idea why you won’t provide the info - unless you’re embarassed I guess.
Without more facts I’ll leave you to chase ghosts.
As I said, there may be an issue, but there may not and you can go and waste a lot of your own time hunting rather than mine.
Provide the info and we can look properly.
As I said. Never, ever, assume………
I’d also be very careful with your licence version and user numbers…….
As you haven’t wanted to divulge that I know you think you are being smart (because most people are straight up and honest), but I can absolutely assure you that they know…… and at some point may do something about it like they have before.
FAFO
Well, I need to have 20 characters minimum for my answer, so here it is: Amen
Yeah we can all play that game.
