Kestrelhttpserver: Transient: After upgrade to aspnet core 2.0 Unable to start Kestrel due to AddressInUseException: Error -4091 EADDRINUSE

Created on 20 Oct 2017 · 27Comments · Source: aspnet/KestrelHttpServer

I tried to deploy webapp that was working previously to azure and it failed to start.
I tried publishing again, and the webapp successfully deployed.
The same thing happened with a different project after I upgraded to aspnet core 2.0 as well.

logs contained this:

2017-10-20 11:27:44.257 +00:00 [Critical] Microsoft.AspNetCore.Server.Kestrel: Unable to start Kestrel.
System.IO.IOException: Failed to bind to address http://127.0.0.1:15364: address already in use. ---> Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions.Internal.AddressInUseException: Error -4091 EADDRINUSE address already in use ---> Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvException: Error -4091 EADDRINUSE address already in use
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.LibuvFunctions.ThrowError(Int32 statusCode)
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.LibuvFunctions.tcp_getsockname(UvTcpHandle handle, SockAddr& addr, Int32& namelen)
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvTcpHandle.GetSockIPEndPoint()
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.ListenTcp(Boolean useFileHandle)
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.CreateListenSocket()
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.<>c.b__8_0(Listener listener)
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.LibuvThread.CallbackAdapter1.<>c.<.cctor>b__3_1(Object callback, Object state) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.LibuvThread.DoPostWork() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.LibuvTransport.<BindAsync>d__20.MoveNext() --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.LibuvTransport.<BindAsync>d__20.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_01.<g__OnBind0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__5.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.AddressesStrategy.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.d__21`1.MoveNext()

and just a bit later

2017-10-20 11:27:56.812 +00:00 [Warning] Microsoft.AspNetCore.Server.Kestrel: Unable to bind to http://localhost:2445 on the IPv6 loopback interface: 'Error -4090 EADDRNOTAVAIL address not available'.

and then

2017-10-20 11:44:20.634 +00:00 [Warning] Microsoft.AspNetCore.Server.Kestrel: Unable to bind to http://localhost:6563 on the IPv6 loopback interface: 'Error -4090 EADDRNOTAVAIL address not available'.

Program.cs is set up like this:

public class Program
    {
        public static void Main(string[] args)
        {
            BuildWebHost(args).Run();
        }
        public static IWebHost BuildWebHost(string[] args) =>
           WebHost.CreateDefaultBuilder(args)
            .UseKestrel()
                .UseContentRoot(Directory.GetCurrentDirectory())
                .UseUrls("http://+:5000")
                .UseAzureAppServices()
                .UseStartup<Startup>()
                .CaptureStartupErrors(true)
                .Build();
    }

Source

oofpez

👍4

Most helpful comment

@halter73 is there anything we can be doing to help move this issue forward? We continue to be affected by it.

mattbrooks2010 on 19 Dec 2017

👍6

All 27 comments

cc @shirhatti

muratg on 27 Nov 2017

I've also encountered this "Failed to bind to address: address already in use" error on aspnet core 2.0 with a webapp on azure failing to start. Restarting the app seemed to fix the issue.

Logs:

---> Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions.Internal.AddressInUseException: Error -4091 EADDRINUSE address already in use
---> Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvException: Error -4091 EADDRINUSE address already in use
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.LibuvFunctions.tcp_getsockname(Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvTcpHandle handle, Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.SockAddr& addr, System.Int32& namelen) at offset 7
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvTcpHandle.GetSockIPEndPoint() at offset 6
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.ListenTcp(System.Boolean useFileHandle) at offset 127
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.CreateListenSocket() at offset 32
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.<>c.b__8_0(Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener listener) at offset 0
at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.CallbackAdapter1.<>c.<.cctor>b__3_1(System.Object callback, System.Object state) at offset 0 at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.LibuvThread.DoPostWork() at offset 78 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(System.Threading.Tasks.Task task) at offset 0 at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.LibuvTransport.<BindAsync>d__20.MoveNext() at offset 450 --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.LibuvTransport.<BindAsync>d__20.MoveNext() at offset 1216 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40 at Microsoft.AspNetCore.Server.Kestrel.Core.<>c__DisplayClass21_01.<g__OnBind0>d.MoveNext() at offset 184
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__5.MoveNext() at offset 119
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__5.MoveNext() at offset 146
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__6.MoveNext() at offset 175
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__7.MoveNext() at offset 506
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressesStrategy.d__2.MoveNext() at offset 149
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__0.MoveNext() at offset 232
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.d__21`1.MoveNext() at offset 281
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Microsoft.AspNetCore.Hosting.Internal.WebHost.d__26.MoveNext() at offset 265
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Microsoft.AspNetCore.Hosting.WebHostExtensions.d__5.MoveNext() at offset 129
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Microsoft.AspNetCore.Hosting.WebHostExtensions.d__4.MoveNext() at offset 290
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 39
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Microsoft.AspNetCore.Hosting.WebHostExtensions.Run(Microsoft.AspNetCore.Hosting.IWebHost host) at offset 21
at Web.Program.Main(System.String[] args) at offset 0

My Program.cs looks like this:

```public class Program
{
public static void Main(string[] args)
{
BuildWebHost(args).Run();
}

    public static IWebHost BuildWebHost(string[] args) =>
        WebHost.CreateDefaultBuilder(args)
            .UseStartup<Startup>()
            .Build();
}

obastow on 1 Dec 2017

@oliverb-1 does it recover?

davidfowl on 1 Dec 2017

@davidfowl Not from what I observed following an incident this morning. We have a single instance of the error logged and posted by @oliverb-1, which occurred at ~2:30am local time. The app was still unresponsive 7 hours later. During this time we were getting HTTP 503 responses from the App Service.

I turned on ASP.NET Core module logs in the web.config, which triggered a process restart resolving the issue.

It might be worth noting that the error log we have was recorded by Exceptionless, which is configured during Startup.Configure. I'm therefore a little puzzled by how this startup error could have been logged at all.

mattbrooks2010 on 1 Dec 2017

@mattbrooks2010 Can you include the log recorded by Exceptionless verbatim? Does it also include Program.Main in the stack trace like @oliverb-1?

halter73 on 1 Dec 2017

@halter73 referring to the same error / incident — we work together 😊

Do you still need me to post something?

mattbrooks2010 on 1 Dec 2017

@mattbrooks2010 I see. Do you have any windows event logs from the "IIS AspNetCore Module" from around ~2:30am local time? If you are running an Azure App Service you can find these in your `D:\home\LogFiles\eventlog.xml".

halter73 on 1 Dec 2017

Yes, I can supply the LogFiles\eventlog.xml file. Can I email this over, rather than post it here?

mattbrooks2010 on 1 Dec 2017

Sure. You can just send the email to the address listed in my github profile.

halter73 on 2 Dec 2017

eventlog.xml supplied on Sun, Dec 3, 2017.

mattbrooks2010 on 6 Dec 2017

I've also experienced a similar issue where an Azure App Service becomes unresponsive, returning 503 errors. In my case, the app remained unresponsive for several hours. Restarting the App Service via the Azure Portal brought the application back online. However, editing and saving the Web.config files via Kudu did not.

Unlike the case reported above, I didn't get a "Failed to bind to address: address already in use" error, I only observed a "Failed to gracefully shutdown process '16296'." error.

@halter73 I've emailed you the relevant eventlog.xml. I hope that this is useful.

cgwrench on 12 Dec 2017

In case this is relevant, this has now occurred in three separate web apps hosted in separate Azure App Services:

2 x ASP.NET Core 1.1 targeting net462
ASP.NET Core 2.0 targeting net462

mattbrooks2010 on 12 Dec 2017

I am affected by this problem also. Just found two webapps unresponsive, returning 503 Service Unavailable. They were brought back to working order by restarting them through the Azure Portal.

mdsharpe on 13 Dec 2017

Here is a possible repro of this issue (or a similar one) on our CI.

ryanbrandenburg on 18 Dec 2017

@ryanbrandenburg The log you linked to ("Microsoft.AspNetCore.Server.Kestrel Critical: Unable to start Kestrel." ...) is the expected output for the ThrowsWhenBinding* Kestrel tests. None of the ThrowsWhenBinding* tests failed in the CI run you linked to. You can verify this by looking at the following log:

[14:27:09] :     [Step 2/2]   [xUnit.net 00:01:31.6599226]   Finished:    Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.FunctionalTests
[14:27:09] :     [Step 2/2]   
[14:27:09] :     [Step 2/2]   Total tests: 615. Passed: 608. Failed: 0. Skipped: 7.
[14:27:09] :     [Step 2/2]   Test Run Successful.
[14:27:09] :     [Step 2/2]   Test execution time: 1.5424 Minutes

The real cause of the failure is #2223. Since the test run failed, the CI reported all of the test logs including the scary "Critical: Unable to start Kestrel." logs which you wouldn't see if the tests had passed.

halter73 on 19 Dec 2017

@halter73 is there anything we can be doing to help move this issue forward? We continue to be affected by it.

mattbrooks2010 on 19 Dec 2017

👍6

@davidfowl The same issue with net core 1.1, 2.0 and waiting for results with net core 2.0.3 I need a couple of weeks to be sure if is affected too.

Azure App Services, different code, different versions of net core and different azure locations. Windows Server Version: 2012. Some app services was updated today to Windows Server 2016, the issue occur randomly and some times affect one instance and some time all instances.

alejandromelis on 22 Dec 2017

I've experienced this plenty of time as well in production. Happens randomly for us, when no deploy is involved, and the app seem to restart successfully.

Running Azure App Service with .NET Standard and net462
net462
win10-x64

System.IO.IOException: Failed to bind to address http://127.0.0.1:32665: address already in use. ---> Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions.Internal.AddressInUseException: Error -4091 EADDRINUSE address already in use ---> Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvException: Error -4091 EADDRINUSE address already in use at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.LibuvFunctions.ThrowError(Int32 statusCode) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.LibuvFunctions.tcp_getsockname(UvTcpHandle handle, SockAddr& addr, Int32& namelen) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvTcpHandle.GetSockIPEndPoint() at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.ListenTcp(Boolean useFileHandle) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.<>c.<StartAsync>b__8_0(Listener listener) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.LibuvThread.DoPostWork() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.LibuvTransport.<BindAsync>d__20.MoveNext() --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.LibuvTransport.<BindAsync>d__20.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_01.<g__OnBind0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__5.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.AddressesStrategy.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.d__211.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Hosting.Internal.WebHost.<StartAsync>d__26.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Hosting.WebHostExtensions.<RunAsync>d__5.MoveNext()

jiimaho on 4 Jan 2018

@davidfowl @halter73 Are you able to tell me if there have been any reports of this since .NET Framework v4.7.1 was rolled out to Azure App Services?

mattbrooks2010 on 10 Jan 2018

@mattbrooks2010 When did this happen? About 5 days ago? I haven't seen any new reports recently now that you mention it.

halter73 on 11 Jan 2018

@halter73 I'm not sure and can't find out much information on it — certainly by the start of this month. Presumably it was a phased roll-out across different regions / data centres.

mattbrooks2010 on 11 Jan 2018

@mattbrooks2010 I just started having this occur in our Azure App Service a few days back. We're using AspNetCore 2.0.1.

joshmouch on 18 Jan 2018

@joshmouch What Azure region and are you targeting .NET Framework or .NET Core?

mattbrooks2010 on 19 Jan 2018

North Central. .Net Framework. This mostly occurs during an auto-scale operation, but I see it during deployment sometimes, too.

joshmouch on 19 Jan 2018

I just started having this occur in our Azure App Service a few days back. We're using AspNetCore 2.1.4.

zmk523 on 7 Feb 2018

👍1

We experienced this today in EU North, target .NET Core 2.0. The app had been running fine for a week, and just died during the night - A restart fixed it, but it's a little iffy having to rely on a manual restart.

We're looking at Auto heal your azure web app to get some inspiration as how to handle it. May serve as inspiration to others as well.

DennisBaekgaard on 8 Mar 2018

We periodically close 'discussion' issues that have not been updated in a long period of time.

We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.