Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-30227

NetworkInterfaceASIO-Replication-0 Tries to connect to non existent host.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • Replication
    • None
    • ALL

    Description

      I am running a MongoDB replica set with 3 nodes.

      The cluster has authentication enabled and has (self signed SSL certificates). SSL mode is set to 'preferred'.

      The version of MongoDB is 3.2.14, and it is the same for all the nodes.

      The `rs.status()` shows that the cluster is working properly. There is one Primary node and 2 Secondary nodes. Secondary nodes are syncing from existing nodes.

      mongoreplicaset:SECONDARY> rs.status()
      {
      	"set" : "mongoreplicaset",
      	"date" : ISODate("2017-07-19T15:02:42.402Z"),
      	"myState" : 2,
      	"term" : NumberLong(32),
      	"syncingTo" : "10.0.16.5:27017",
      	"heartbeatIntervalMillis" : NumberLong(2000),
      	"members" : [
      		{
      			"_id" : 5,
      			"name" : "10.0.16.5:27017",
      			"health" : 1,
      			"state" : 1,
      			"stateStr" : "PRIMARY",
      			"uptime" : 606374,
      			"optime" : {
      				"ts" : Timestamp(1500476413, 2),
      				"t" : NumberLong(32)
      			},
      			"optimeDate" : ISODate("2017-07-19T15:00:13Z"),
      			"lastHeartbeat" : ISODate("2017-07-19T15:02:41.235Z"),
      			"lastHeartbeatRecv" : ISODate("2017-07-19T15:02:40.460Z"),
      			"pingMs" : NumberLong(0),
      			"electionTime" : Timestamp(1499870258, 1),
      			"electionDate" : ISODate("2017-07-12T14:37:38Z"),
      			"configVersion" : 2932125
      		},
      		{
      			"_id" : 101,
      			"name" : "10.0.16.101:27017",
      			"health" : 1,
      			"state" : 2,
      			"stateStr" : "SECONDARY",
      			"uptime" : 606595,
      			"optime" : {
      				"ts" : Timestamp(1500476413, 2),
      				"t" : NumberLong(32)
      			},
      			"optimeDate" : ISODate("2017-07-19T15:00:13Z"),
      			"syncingTo" : "10.0.16.5:27017",
      			"configVersion" : 2932125,
      			"self" : true
      		},
      		{
      			"_id" : 144,
      			"name" : "10.0.16.144:27017",
      			"health" : 1,
      			"state" : 2,
      			"stateStr" : "SECONDARY",
      			"uptime" : 606233,
      			"optime" : {
      				"ts" : Timestamp(1500476413, 2),
      				"t" : NumberLong(32)
      			},
      			"optimeDate" : ISODate("2017-07-19T15:00:13Z"),
      			"lastHeartbeat" : ISODate("2017-07-19T15:02:41.335Z"),
      			"lastHeartbeatRecv" : ISODate("2017-07-19T15:02:40.693Z"),
      			"pingMs" : NumberLong(0),
      			"syncingTo" : "10.0.16.101:27017",
      			"configVersion" : 2932125
      		}
      	],
      	"ok" : 1
      }
      

      Yet, in the logs, we get every 30 seconds the following error:

      2017-07-19T17:01:33.459+0200 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to 10.0.16.155:27017 - ExceededTimeLimit: Operation timed out
      2017-07-19T17:01:33.459+0200 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to 10.0.16.155:27017
      

      This address is not defined anywhere.

      We face the same issue with every MongoDB replica set. Each time the address they try to connect is different, but the error the same.

      Attachments

        1. mongodb.node1.log
          7.26 MB
        2. mongodb.node2.log
          6.39 MB
        3. mongodb.node3.log
          5.17 MB

        Activity

          People

            mark.agarunov Mark Agarunov
            kbessas.sentia Konstantinos Bessas
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: