We have a MongoDb replicaset set up on three nodes, and we have this in both errorlog. This is an example. All of them at same time in the different nodes.
Mar 27 10:31:49
Node 1:
Mar 27 10:31:49 ulpmon01 mongod.27017[1464]: [rsHealthPoll] replSet info ulpmon03.osasunet:27017 is down (or slow to respond):
Mar 27 10:31:49 ulpmon01 mongod.27017[1464]: [rsHealthPoll] replSet member ulpmon03.osasunet:27017 is now in state DOWN
Mar 27 10:31:53 ulpmon01 mongod.27017[1464]: [rsHealthPoll] replSet member ulpmon03.osasunet:27017 is up
Mar 27 10:31:53 ulpmon01 mongod.27017[1464]: [rsHealthPoll] replSet member ulpmon03.osasunet:27017 is now in state SECONDARY
Node 2:
Mar 27 10:31:43 ulpmon02 mongod.27017[1438]: [rsHealthPoll] DBClientCursor::init call() failed
Mar 27 10:31:43 ulpmon02 mongod.27017[1438]: [rsHealthPoll] replSet info ulpmon03.osasunet:27017 is down (or slow to respond):
Mar 27 10:31:43 ulpmon02 mongod.27017[1438]: [rsHealthPoll] replSet member ulpmon03.osasunet:27017 is now in state DOWN
Mar 27 10:31:50 ulpmon02 mongod.27017[1438]: [rsHealthPoll] replset info ulpmon03.osasunet:27017 heartbeat failed, retrying
Mar 27 10:31:53 ulpmon02 mongod.27017[1438]: [rsHealthPoll] replSet member ulpmon03.osasunet:27017 is up
Mar 27 10:31:53 ulpmon02 mongod.27017[1438]: [rsHealthPoll] replSet member ulpmon03.osasunet:27017 is now in state SECONDARY
Node 3:
Mar 27 10:31:53 ulpmon03 mongod.27017[1442]: [rsHealthPoll] replset info ulpmon01.osasunet:27017 thinks that we are down
Mar 27 10:31:53 ulpmon03 mongod.27017[1442]: [rsHealthPoll] replset info ulpmon02.osasunet:27017 thinks that we are down
Can anyone help?