Start the MongoDB shell and initiate the replica set:
mongo
> rs.initiate()
The output of the command should look like this:
{
"info2" : "no configuration specified. Using a default configuration for the set",
"me" : "127.0.0.1:27017",
"ok" : 1,
"operationTime" : Timestamp(1538772048, 1),
"$clusterTime" : {
"clusterTime" : Timestamp(1538772048, 1),
"signature" : {
"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
"keyId" : NumberLong(0)
}
}
}
rs01:SECONDARY>
Note the "ok" value should be 1. Any other value, i.e. 93, means something is wrong.
Hit enter, you should see your prompt turn into rs01:PRIMARY>, this indicates the replica set is being used. Type exit to get back to your regular shell:
Depending on your network settings, including /etc/hosts and DNS, if you have configured Rocket.Chat to use localhost:27017 you may see an error similar to this:
[conn1] created this configuration for initiation : { _id: "rs0", version: 1, members: [ { _id: 0, host: "test:27017" } ] }
rs.initiate() may be defaulting to the host name e.g. 'test'
You can force a different hostname as follows:
You should get a response similar to:
Reconfigure and restart Rocket.Chat service
After you configured the replica set, you MUST add the MONGO_OPLOG_URL environment variable to the service definition and restart Rocket.Chat server.
In CentOS open file /usr/lib/systemd/system/rocketchat.service
In Ubuntu or Debian open file /lib/systemd/system/rocketchat.service