Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rocket.Chat 1.0.0 stopped working with Percona server for MongoDB 3.6 #14298

Closed
thaiphv opened this issue Apr 29, 2019 · 2 comments · Fixed by #14299
Closed

Rocket.Chat 1.0.0 stopped working with Percona server for MongoDB 3.6 #14298

thaiphv opened this issue Apr 29, 2019 · 2 comments · Fixed by #14299
Milestone

Comments

@thaiphv
Copy link
Contributor

thaiphv commented Apr 29, 2019

Description:

We have been running Rocket.Chat with Percona server for MongoDB 3.6 for several months without any issues. However, after upgrading to the latest release 1.0.0, all of Rocket.Chat instances stopped working

Expected behavior:

Rocket.Chat 1.0.0 should work with Percona server for MongoDB 3.6 as it is compatible with MongoDB 3.6.

Server Setup Information:

  • Version of Rocket.Chat Server: 1.0.0
  • Operating System: Ubuntu 16.04
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 8.11.4
  • MongoDB Version: 3.6.8-2.0

Additional context

I believe this issue is caused by the semver module, which doesn't understand the version string 3.6.8-2.0 and consider it an older version of MongoDB and the fix should be simple.

Relevant logs:

YOUR CURRENT MONGODB VERSION IS NOT SUPPORTED, PLEASE UPGRADE TO VERSION 3.2 OR LATER

@rodrigok
Copy link
Member

Thanks @thaiphv we are shipping version 1.0.1 with some fixes, we will check your PR and ship 1.0.2 tomorrow.

@rodrigok rodrigok added this to the 1.0.2 milestone Apr 29, 2019
@fabien4455
Copy link

i have a problem when upgrading to 1.0.1.... I'll send a issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants