[SERVER-65953] unexpected IP/Port logged in "connection handshake" error Created: 26/Apr/22  Updated: 22/Jun/22  Resolved: 27/May/22

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

Type: Bug Priority: Major - P3
Reporter: Debalina Saha Assignee: Chris Kelly
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Error :
error msg="Cannot con
nect to MongoDB: cannot connect to MongoDB: server selection error: server selection timeout, current topology: { Type: Single, Servers: [

{ Addr: host2:port, Type: Unknown, Last error: connection() error occured during connection handshake: dial tcp 127.0.0.1:27017: connect: connection refused }

, ] }

Note: 127.0.0.1:27017 is not our host/port, not sure of this line in the log

Got this error on one VM(azure), which is part of a mongodb replicaset.
We faced an issue from application end yesterday.
During the issue duration , affected host was secondary, it became primary after an election happened thereafter.

We checked and found No health event reported for this VM.

Issue resolved on its own. But we are not sure of this error and as this is prod env we are trying to investigate.
We are using Mongo 4.4.6 version on Azure VM



 Comments   
Comment by Chris Kelly [ 27/May/22 ]

Roger, thanks! I'll go ahead and close this ticket then.

Christopher

Comment by Debalina Saha [ 27/May/22 ]

We are not facing that issue anymore. We suspected it to be an issue from VM. We have replaced the VM.

Sorry for late reply.

Comment by Chris Kelly [ 27/May/22 ]

Hi Debalina,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please submit the requested information?

Regards,
Christopher

Comment by Chris Kelly [ 05/May/22 ]

Hi Debalina,

In order to look into this some more, we will need some additional information.

I've created a secure upload portal for you. Files uploaded to this portal are hosted on Box, are visible only to MongoDB employees, and are routinely deleted after some time.

For each node in the replica set spanning a time period that includes the incident, would you please archive (tar or zip) and upload to that link:

  • the mongod logs
  • the $dbpath/diagnostic.data directory (the contents are described here)
  • the contents of your configuration file if you're using one, or your command line parameters if not.
  • the output of the following command:
    •  lsof -n | grep 27017

Regards,
Christopher

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