Rocket.Chat Version: 1.0.1 --> Fail install #14303
Milestone
Comments
|
Read your log error. https://go.rocket.chat/i/oplog-required Which actually goes here: A decision was made to enforce oplogs, but unless you read the release notes (you really should) you won't notice. |
|
That's so smart that when you want to downgrade to avoid 1.0.1 it's fucked up. Rocket Chat is broken... Actually I'm happy to do this in a test environment... Rocket Chat is going to be less and less good with these stupid modifications... Why if it doesn't work we can't downgrade to 0.X.X ?? Before downgrading was working... This 1.0.X is so bad... |
|
Before upgrading you should always do a full database backup, and make a copy of the old Rocket.Chat server folder. That's all you need to revert back to any previous version. |
|
I did it ;) my rocketchat is safe. Thank's for the advice BTW |
|
Ok i added OPLOG.. but not working ;) |
|
The problem is not anymore OPLOG.. But rocketchat that can't see mongodb version.. But why ? |
|
i tried to switch with mongoadmin account at the line :
So now it's
it works but that's really unsecure... Why it's not working with rocket user now ? ... |
|
Can you paste long logs like that on a gist or something ? It clutters the issue and makes it hard to read. Just paste relevant snippets - probably this:
Then you would search Issues and probably find this. |
|
I'll upload the logs please wait. |
|
Ok even if i use Rocket user, it works. the only problem is : RocketChat don't say that rocketchat is up on IP:3000 ( in terminal ) |
|
Docker composing with admin user // in rocketchat administration :
Docker composing with rocket user // in rocketchat administration :
Here the files : docker-compose up-rocket_user.log |
|
I think the problem is : adding mongo version check in administration make trouble for docker compose. If rocketchat can't access to admin user he can't know mongo version So it doesn't tell that rocketchat is working.. |
|
@fabien4455 you can add the role More information in this thread DataDog/dd-agent#318 (comment) |
Note to self: never run rocketchat in kubernetes with :latest tag.. A simple restart might kill everything |
|
Ok it works ! I ran : db.runCommand({grantRolesToUser:"rocket",roles:["clusterMonitor"]}) And now it's working ;) thank's |
|
@fabien4455 great, we will add that to the error logs and our documentation. |
|
Perfect, you can close the issue :) |
|
@fabien4455 will keep it open until we add the info into the error log and docs, then will close. |
|
Just a stupid question.... people using rocket.chat on a single VM... how do we deal with the new "replica" requirement ? |
|
@fabien4455 Did you "migrate" from a rocketchat setup using a single VM or you already have a mongo setup using multiple instance ? |
|
@PointPubMedia you do not need multiple mongodb instances, just need to enable the replicaset mode in your single instance to enable the oplog stream where Rocket.Chat listen for data changes. |
|
@rodrigok Would really need some help with our setup on Debian :( |
|
@PointPubMedia contact me at https://open.rocket.chat/direct/rodrigo.nascimento please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
I was in 0.73.2. I tried to update to 1.0.1 i got SERVER ERROR.
I restored my snapshot and i tried to update 0.74.3. Success. I think that the problem is the new version of RocketChat that does not recognize my mongodb version
Steps to reproduce:
Expected behavior:
RocketChat installing successfully
Actual behavior:
Server Setup Information:
Relevant logs:
Please see my files. the zip is how i deploy rocketchat ( i removed passwords so don't try to hack me, plus it's internal so... ;) .... )
The log is how rocketchat react...
docker-compose up.log
rocketchat.zip
Other informations:
I was before in 3.2.. i upgraded to 3.4 then 3.6 then 4.0.8 ! But the upgrade from 0.73.2 to 0.74.3 was a success ! So... I don't think that's the problem is from mongodb upgrade.. I think rocketchat 1.0 doesn't support 4.0.8 mongodb ??
The text was updated successfully, but these errors were encountered: