net: DialTimeout w/ "udp4" or "udp6" failing #31058
Closed
Labels
Milestone
Comments
Sounds like the DNS stub resolver is broken in Go 1.12 and 1.12.1. Can you please confirm that the issue still happens when GODEBUG=netdns=go on non-Windows platforms. If not, the root cause is probably #30521. |
I don't have access to non-Windows platform - sorry. Will cross post to other repo to see if anyone there can try. |
User on Mac replied with: when using the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, however, it is not present in v1.11.5 (this is last known good version).
What operating system and processor architecture are you using (
go env
)?go env
OutputWindows 10 Professional Version 1809 (OS Build 17763.379) x64
MongoDB version 3.6.11
Golang version 1.12.1
What did you do?
Using the MGO driver (github.com/globalsign/mgo) to connect to a MongoDB instance using the driver's Dial function.
Sample code:
What did you expect to see?
On versions prior to 1.12.1 the connection to local Mongo is established in less than a second and a correct session and no error is returned from the function. Code is then able to connect and execute against MongoDB.
What did you see instead?
Attempts to connect run for ~10 seconds before timing out. No connection is established, no connection request is seen in the Mongo logs and the session creation fails - program terminates.
The issue has been raised on the driver's Git pages (see globalsign/mgo#338 (comment)) however, initial debugging points to change in Go
net
package issue instead of mgo driver.The text was updated successfully, but these errors were encountered: