Issue After Updating Server from Version 8.0.1 to 8.6.1

Community Support
1

Description

Hi,
I’m reaching out regarding an issue with my server after updating from version 8.0.1 to 8.6.1. The update process ran smoothly with no errors, and the desktop app confirmed that the server was successfully updated to 8.6.1.
However, when I log back in after the update, all previous conversations disappeared. Additionally, I’m unable to send new messages, as they vanish immediately after being sent. (All users can log in)
Can this issue still be fixed post-update, or should I revert to the previous server snapshot and attempt to resolve it there?
Best regards,
Chester

Server Setup Information

  • Version of Rocket.Chat Server:
  • Operating System: Ubuntu 22.04.5 LTS
  • Deployment Method: Ubuntu Manual installation
  • Number of Running Instances: 1 (edited 23 users)
  • DB Replicaset Oplog: Disabled
  • NodeJS Version: v22.16.0
  • MongoDB Version: 8.2.4 / wiredTiger
  • Proxy: None
  • Firewalls involved:

Any additional Information

Database check results:
rs01 [direct: primary] rocketchat> db.rocketchat_message.countDocuments()
759
rs01 [direct: primary] rocketchat> db.rocketchat_room.countDocuments()
54
rs01 [direct: primary] rocketchat> db.users.countDocuments()
14
I’ve performed similar updates before and never encountered this issue. I’m extremely concerned that critical internal data may have been lost, especially since version support will end on August 1.

2

Seriously?

It would not be normal to just lose data without a big change somewhere. However, jumping several releases is never a good idea. Personally I’d have done as per the docs so 8.0 → 8.1 → 8.2 etc.

What licence are you using and how many users?

3

My apologies. Not 23 instances, but 23 users of 1 instance, and we are using the starter license. I’ve done a sequential update due to a MongoDB version update over the last six months, but in previous years I jumped to multiple version updates and encountered no issue at all.

My suspicion here is the database oplog replica is disabled.

I will try this one by updating the versions 1 at a time and get back to this thread once I get a result.

Thank you.