[CSHARP-3117] Fix timeout connecting to server on Linux Created: 28/May/20 Updated: 28/Oct/23 Resolved: 09/Jun/20 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Connectivity |
| Affects Version/s: | 2.11.0-beta1 |
| Fix Version/s: | 2.11.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | José Massada | Assignee: | Vincent Kam (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Docker debian |
||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Hi, I'm in the process of updating several applications to .NET Core and after updating the MongoDB driver to version 2.11.0-beta1 our deploys started to fail. After quite a lot of trial and error I found a StackOverflow question from 19 days ago detailing the same error we were getting: The only answer mentions that manually resolving the server hostnames fixes the error. I've tried and indeed fixed our deploy issues. The same answer mentions that this issue was fixed a long time ago, is this a regression? Thanks, Jose Error:
Workaround:
|
| Comments |
| Comment by Vincent Kam (Inactive) [ 09/Jun/20 ] |
|
This fix will be included as part of 2.11.0-beta2! Thank you so much to all the reporters for bringing this to our attention! |
| Comment by Githook User [ 09/Jun/20 ] |
|
Author: {'name': 'rstam', 'email': 'robert@robertstam.org', 'username': 'rstam'}Message: |
| Comment by Vincent Kam (Inactive) [ 08/Jun/20 ] |
| Comment by José Massada [ 29/May/20 ] |
|
Found this: According to that issue, enabling KeepAlive breaks Connect, which is being enabled here: |
| Comment by José Massada [ 28/May/20 ] |
|
https://github.com/dotnet/runtime/issues/16263#issuecomment-207553272
It looks like dotnet core can't connect by host in linux, |
| Comment by José Massada [ 28/May/20 ] |
|
Found this in the source code: For NETSTANDARD1_5 || NETSTANDARD1_6 the hostname is being resolved but not for .NET standard 2.0 |
| Comment by José Massada [ 28/May/20 ] |
|
Forgot to mention that we only see the issue within a linux docker container. |