Recover MongoDB with Data
This procedure assumes that you have performed the procedure required to Recover and Rejoin a Cluster after a CCO Server Failure as provided in CCO Troubleshooting.
By default, Mongo DB only listens on the Loopback IP and does not try to rejoin a cluster.
To recover MongoDB and ensure that it rejoins the Cluster, follow this procedure.
Modify the MongoDB configuration file to listen on all Interfaces.
Compare the file version on CCO3 to the ones on either CCO1 or CCO (assuming CCO3 is the newly-recovered VM.
Verify it is now Listening on 0.0.0.0 instead of 127.0.0.1.
Using the Mongo DB CLI client, check the status of the Cluster.
In one of the three Replication Sets, you should see one that has "self" set to true.
The IP in this set should match the IP of the CCO node you replaced.
You should also see it's "stateStr" as "SECONDARY".
Verify if the MongoDB Service is Running on the CCO
To verify if the MongoDB service is running on the CCO, follow this procedure:
Login to theVM as the .
Change to the system directory.
Verify the status of the MongoDB service.
Next, verify the status of the CCO service.
- No labels