7
016-03-07T09:10:16.992-0600 W NETWORK  [HostnameCanonicalizationWorker] Failed to obtain name info for: [ (1*.*.**.***, "Name or service not known"), (1*.*.**.***, "Name or service not known"), (1*.*.**.***, "Name or service not known") ]
2016-03-07T09:25:17.041-0600 W NETWORK  [HostnameCanonicalizationWorker] Failed to obtain name info for: [ (1*.*.**.***, "Name or service not known"), (1*.*.**.***, "Name or service not known"), (1*.*.**.***, "Name or service not known") ]
2016-03-07T09:40:17.085-0600 W NETWORK  [HostnameCanonicalizationWorker] Failed to obtain name info for: [ (1*.*.**.***, "Name or service not known"), (1*.*.**.***, "Name or service not known"), (1*.*.**.***, "Name or service not known") ]

1*... : is my IP Address

My Cluster is 3 node replica set Buit with MongoDB 3.2.

i never seen this kind of errors logging in my other environments.

what might be issue causing this.

Marc B
  • 356,200
  • 43
  • 426
  • 500
rohith
  • 71
  • 1
  • 5
  • this looks clunky, please specify technology and client settings – profesor79 Mar 07 '16 at 16:58
  • this is related to MongoDB – rohith Mar 07 '16 at 17:01
  • yes this is related to mongodb – rohith Mar 16 '16 at 21:53
  • 1
    This issue is from Os level host file,as IPV6 is disabled .so modified hostfile accordingly without IPV6 config on host file.now it works without any failed events. – rohith Mar 18 '16 at 16:24
  • reverse lookup of dns is not passing thorough which had been configured using pointer . – rohith Apr 12 '16 at 15:45
  • I encountered the same problem on Microsoft Azure. It looks like our cluster is loosing connection between some servers from time to time. As a result i get `{ "code" : 50, "ok" : 0, "errmsg" : "Operation timed out" }` for commands such as `sh.shardCollection`, `db.count` (for large collections > 1 billion docs) and have problem during balancing `Last reported error: could not get updated shard list from config server due to ExceededTimeLimit Operation timed out` Any luck fixing the problem? – Jörg Rech Apr 18 '16 at 07:12
  • i will try look into your issue .. – rohith Apr 21 '16 at 22:06
  • 1
    any luck with finding a solution here? – Grzegorz Gajos Oct 25 '16 at 13:47
  • This is IPV6 issue ... where reverse lookup of dns is being failed in firewall .. – rohith Dec 07 '16 at 21:37

1 Answers1

1

Answer is very simple, node cannot resolve name from IP address. Please add those addresses and correlating names to: /etc/hosts -file

12.345.678.90  node1  node1.my.domain
12.345.678.91  node2  node2.my.domain
JJussi
  • 1,540
  • 12
  • 12