[GODRIVER-835] Querying Atlas sandbox cluster returns server selection timeout Created: 18/Feb/19 Updated: 14/Mar/19 Resolved: 14/Mar/19 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | Connections |
| Affects Version/s: | 0.3.0, 0.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Junaid Warwani | Assignee: | Scott L'Hommedieu (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Atlas Sandbox replica cluster with 3 nodes, deployed on AWS M0 instances, Version 4.0.6 |
||
| Issue Links: |
|
||||||||
| Description |
|
I'm able to connect to an Atlas-hosted sandbox replica set cluster, but running any subsequent query (e.g. drop collection) is returning the following error:
The code I'm using to connect is this:
Connecting via Python works:
|
| Comments |
| Comment by Scott L'Hommedieu (Inactive) [ 14/Mar/19 ] | ||||||||
|
DUP OF | ||||||||
| Comment by Junaid Warwani [ 13/Mar/19 ] | ||||||||
|
You're right! It is related to | ||||||||
| Comment by Scott L'Hommedieu (Inactive) [ 12/Mar/19 ] | ||||||||
|
Can you provide your system info and go version. It's possible that there are some issues related to | ||||||||
| Comment by Junaid Warwani [ 12/Mar/19 ] | ||||||||
|
Why would I have an issue with validating the cert with the go driver but not the python driver or the mongo shell? What is the go driver doing that's different than the python driver / mongo shell? I'm able to connect and run queries with the mongo shell, so I'm failing to see how this could be an issue on my side, unless you've got a suggestion? | ||||||||
| Comment by Scott L'Hommedieu (Inactive) [ 12/Mar/19 ] | ||||||||
|
It looks like you are having issues specifically with validating x509 certs. The error is occuring on first operation because the driver has deferred the connection and auth until the operation occurs.
| ||||||||
| Comment by Junaid Warwani [ 22/Feb/19 ] | ||||||||
|
I tried running your code, and got the same error. It panicked after getting an error at `insertResult, err := collection.InsertOne(context.TODO(), ash)`:
I do have the latest go driver–version 0.3.0. Our Atlas cluster has the following config:
It is also connected to our VPC via Peering. | ||||||||
| Comment by Scott L'Hommedieu (Inactive) [ 22/Feb/19 ] | ||||||||
|
I've run this code successfully against an atlas 4.0.6 3 node replset. Can you try this in your setup and report back the results? Do you have the latest go driver? Can you share config details of your atlas cluster?
| ||||||||
| Comment by Junaid Warwani [ 22/Feb/19 ] | ||||||||
|
Additionally, the code works with mongo running locally. | ||||||||
| Comment by Junaid Warwani [ 22/Feb/19 ] | ||||||||
|
I have confirmed that I can connect with pymongo and with the shell, and run queries on both. I'm only having trouble with the go driver, where I can connect but any subsequent query is failing. | ||||||||
| Comment by Junaid Warwani [ 22/Feb/19 ] | ||||||||
|
I don't know what other details would be relevant. Ours is a sandbox cluster–not sure if that makes a difference. Is there anything else that could affect this? Is there some sort of configuration dump I can get from our cluster that might help you debug the issue? | ||||||||
| Comment by Scott L'Hommedieu (Inactive) [ 21/Feb/19 ] | ||||||||
|
I don't have any issue running this code (with driver on master) or other examples against a 4.0.6 3-node repl set in Atlas. Are there any other details that I'm missing? |