Replica Sets Troubleshooting

can't get local.system.replset config from self or any seed (EMPTYCONFIG)

Set needs to be initiated. Run rs.initiate() from the shell.

If the set is already initiated and this is a new node, verify it is present in the replica set's configuration and there are no typos in the host names:

> // send to a working node in the set:
> rs.conf()

Replication halts with "objects in a capped ns cannot grow" (assertion 10003)

Generally this happens if you have a capped collection without an _id index and you are using a custom _id.

To fix, make sure that any capped collections you are using have a unique index on the _id field and resync the halted slave.

"couldn't initiate : can't find self in the replset config my port: 27017" under Mac OS X

Generally this happens because your hostname and computer name do not match. The safest solution is to supply a config object to rs.initiate. Another solution is to:

Open System Preferences, select the Sharing page, and set your Computer Name at the top. Then open Terminal and run

$ sudo hostname (name chosen above including the .local at the end)

It will prompt you for your password. Once the command has finished, rs.initiate should work.

"not electing self, not all members up and we have been up less than 5 minutes"

The idea here is that if a bunch of nodes bounce all at once, we don't want to drop data
if we don't have to – we'd rather be offline and wait a little longer instead. Once a node
has been up for five minutes, it is eligible to be primary as long as it can achieve a majority.
In addition, if all members are up, a member can become primary immediately.