[COMPASS-4534] Unable to connect with v1.24.1 - Error: getaddrinfo ENOTFOUND mongodb Created: 10/Dec/20 Updated: 29/Oct/23 Resolved: 17/Dec/20 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Compass |
| Affects Version/s: | 1.24.1 |
| Fix Version/s: | 1.24.6 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Lester Waters | Assignee: | Rhys Howell |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 10 Desktop |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Documentation Changes: | Not Needed | ||||||||||||
| Sprint: | Iteration Star Apple | ||||||||||||
| Description |
| Comments |
| Comment by Githook User [ 16/Dec/20 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(connectivity): use older driver defaults for directConnection and readPreference |
| Comment by Githook User [ 16/Dec/20 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: Revert "fix(connection-model): directConnection and readPreference connectivity fix This reverts commit b10a3dfd11f4d0e873db11db915ffa6950a75ab0. |
| Comment by Githook User [ 16/Dec/20 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(connectivity): use older driver defaults for directConnection and readPreference |
| Comment by Githook User [ 16/Dec/20 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: Revert "fix(connection-model): directConnection and readPreference connectivity fix This reverts commit b10a3dfd11f4d0e873db11db915ffa6950a75ab0. |
| Comment by Githook User [ 16/Dec/20 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: Revert "fix(connection-model): directConnection and readPreference connectivity fix This reverts commit b10a3dfd11f4d0e873db11db915ffa6950a75ab0. |
| Comment by Alex Richards [ 15/Dec/20 ] |
|
I also experienced this problem but the error message I had was connection timeout. This was when trying to use an SSL tunnel to connect to my MongoDB instance. Resolved the issue by rolling back from 1.24 > 1.23 |
| Comment by Githook User [ 15/Dec/20 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(connection-model): directConnection and readPreference connectivity fix |
| Comment by Githook User [ 15/Dec/20 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix(connection-model): directConnection and readPreference connectivity fix |
| Comment by Githook User [ 14/Dec/20 ] |
|
Author: {'name': 'Rhys', 'email': 'Anemy@users.noreply.github.com', 'username': 'Anemy'}Message: fix: set directConnection true on direct connections |
| Comment by Massimiliano Marcon [ 14/Dec/20 ] |
|
Thank you for the detailed bug report. We are investigating the problem and hopefully we'll have a fix or a workaround soon. |
| Comment by Ran Schindler [ 13/Dec/20 ] |
|
I have the same issue while trying to connect to a mongo instance through a tunnel Could it be that while creating new connection on Mongo Compass 1.24.1 the UI try to discover the entire replica set topology and connect to the primary/secondary IP. Is there a way to create a DIRECT connection to an HOST/IP+Port just like the clients api and disable the topology discovery step? From pymongo documentation: directConnection (optional): if True, forces this client to connect directly to the specified MongoDB host as a standalone . If false, the client connects to the entire replica set of which the given MongoDB host(s) is a part |
| Comment by Lester Waters [ 13/Dec/20 ] |
|
Curious. In this case, there is no replica set configured (single node instance used for testing). Why would it work with v1.23.0 and not with v1.24.0? This is readily reproducable on multiple VMs with the exact same connection string on multiple VMs. I can connect with v1.23.0 and as soon as I upgrade, I cannot connect. If I uninstall v1.24.1 and reinstall v1.23.0, it starts working again.
|
| Comment by Alex Kubacki [ 12/Dec/20 ] |
I don't believe this is the case. From my tests with 1.24.1 (as compared to 1.23.0) what I see is:
In your case, it looks like you're connecting to a (redacted) "HOSTNAME.com:27017", and your replica set configuration has the node address of "mongodb:27017". Hence, your error:
I don't know yet how to work around this, other than to use split-horizon DNS in my case, so if there's a at least a connection parameter to connect in a "single node" |