[SERVER-23363] ReplicaSet heartbeat requests failing to connect Created: 26/Mar/16  Updated: 28/Mar/16  Resolved: 28/Mar/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.2.0
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: Krishnan Kannan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I have setup a replica set with 2 members and 1 arbiter. In the following log,
europa is a replica set member and mercury is the arbiter. Though all 3 instances are running, I keep getting the connection refused error.

016-03-26T23:37:03.977+0000 I REPL [ReplicationExecutor] Error in heartbeat request to mercury:27017; Location18915 Failed attempt to connect to mercury:27017; couldn't connect to server mercury:27017 (10.x.x.x), connection attempt failed
2016-03-26T23:37:05.437+0000 W NETWORK [ReplExecNetThread-1] Failed to connect to 10.x.x.x:27017, reason: errno:111 Connection refused
2016-03-26T23:37:05.437+0000 I REPL [ReplicationExecutor] Error in heartbeat request to europa:27017; Location18915 Failed attempt to connect to europa:27017; couldn't connect to server europa:27017 (10.x.x.x), connection attempt failed
2016-03-26T23:37:05.439+0000 W NETWORK [ReplExecNetThread-1] Failed to connect to 10.x.x.x:27017, reason: errno:111 Connection refused
2016-03-26T23:37:05.439+0000 I REPL [ReplicationExecutor] Error in heartbeat request to europa:27017; Location18915 Failed attempt to connect to europa:27017; couldn't connect to server europa:27017 (10.x.x.x), connection attempt failed
2016-03-26T23:37:05.439+0000 W NETWORK [ReplExecNetThread-1] Failed to connect to 10.x.x.x:27017, reason: errno:111 Connection refused
2016-03-26T23:37:05.440+0000 I REPL [ReplicationExecutor] Error in heartbeat request to europa:27017; Location18915 Failed attempt to connect to europa:27017; couldn't connect to server europa:27017 (10.x.x.x), connection attempt failed
2016-03-26T23:37:05.589+0000 I REPL [ReplicationExecutor] waiting for 4 pings from other members before syncing
2016-03-26T23:37:05.979+0000 W NETWORK [ReplExecNetThread-1] Failed to connect to 10.x.x.x:27017, reason: errno:111 Connection refused
2016-03-26T23:37:05.979+0000 I REPL [ReplicationExecutor] Error in heartbeat request to mercury:27017; Location18915 Failed attempt to connect to mercury:27017; couldn't connect to server mercury:27017 (10.x.x.x), connection attempt failed
2016-03-26T23:37:05.980+0000 W NETWORK [ReplExecNetThread-1] Failed to connect to 10.x.x.x:27017, reason: errno:111 Connection refus



 Comments   
Comment by Kelsey Schubert [ 28/Mar/16 ]

Hi kxkannan,

Thank you for the follow up. Since you were able to resolve this issue, I will be closing this ticket.

For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag.

Kind regards,
Thomas

Comment by Krishnan Kannan [ 27/Mar/16 ]

This was due to each of the mongodb instance listening only on 127.0.0.1. I changed the bindIp to listen on the internal IP address and the connections between the mongo instances started working fine.

Generated at Thu Feb 08 04:03:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.