...

> rs.status()
{
 "startupStatus" : 1,
 "ok" : 0,
 "errmsg" : "loading local.system.replset config (LOADINGCONFIG)"
}

2 - Preferred steps

We recommend first trying to reconfigure the Mongo cluster using the steps on this link.

...

1. First choose a container in your mongo addon - preferrably the last master if you can identify it

   Code Block
   nex-cli cubes --addon name_of_mongo_addon

    

2. Stop all other mongo containers

   Code Block
   nex-cli cubes:stop other_container_id

   
   

3. SSH to the rack hosting the container that is still alive

   Code Block
   nex-cli racks:ssh 10.1.1.1

   
   

4. Connect to the container

   Code Block
   sudo nex-attach my_container_id

    

5. Connect to Mongo using the Shell

   Infocode
   mongo -u $MONGO_USER -p $MONGO_PASSWORD admin

   
   

6. Delete the local replication information. This command does NOT delete your actual data but will destroy uncommitted replication transactions.

   Code Block
   use local db.dropDatabase()

   
   

7. Exit the MongoShell and the container

8. On the rack issue a restart of the container. Upon restart the mongo instance will initiate a new replicaSet (previous one being deleted)

   Code Block
   # Restart nex-restart --name my_container_id # Monitor logs docker logs -f my_container_id

   
   

9. Exit the rack and bring up the other nodes using the nex-cli

   Code Block
   nex-cli cubes:start other_container_id