-
Notifications
You must be signed in to change notification settings - Fork 524
.NET Core 2.1: UvException: Error -107 ENOTCONN socket is not connected #2920
Comments
Did you recently upgrade to 2.1 by any chance? I wonder if you may have an older container running still. Because like you said, it should have been fixed already. Can you run |
dotnet info in running container
logs looks like this |
That looks good. I am not sure why you would still get these logs. Any chance you recently update to 2.1 and you had the logs from a previous deployment? |
As i said - last container build and deploy - 23 august 2018. |
@OXEXIVO I'm certain that either something wasn't updated to 2.1.3 or that the logs occurred prior to the upgrade taking effect. Starting in 2.1.3, there is nothing that logs "ListenerSecondary.OnConnection" anymore. The "ListenerSecondary.OnConnection" and "Listener.OnConnection" logs should be replaced with debug level logs containing Can you provide us with the output of |
|
|
@ZOXEXIVO And you're sure you're still seeing new "Listener(Secondary).OnConnection" logs? Those are logged by Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.dll, and your lsof output doesn't show that assembly as loaded. Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.dll, which is loaded, doesn't create those logs. |
@halter73 Last error date - 12 September, and we not changing anything on server (before/after 09/12) |
@ZOXEXIVO You should look at the dependences for the process logging that error. That error is simply not logged by in anywhere in Kestrel 2.1.3. Moreover, that error isn't logged by any version of the Sockets transport. |
After fix IO.Pipelines CPU spikes we migrate to Sockets transport. |
Last week see see this error in our logs:
It should be fixed with changing loglevel in v2.1 release #2045, #2583, #2658, but we see it now
We use this packages:
and build app with docker image
microsoft/dotnet:2.1-sdk
and run it with
microsoft/dotnet:2.1-aspnetcore-runtime
Last build date from container - 23 August 2018
The text was updated successfully, but these errors were encountered: