ASP.NET Core 2、IIS应用池崩溃并停止

我刚刚将一个web应用程序更新为ASP.NET Core 2.0，该应用程序在Windows Server 2008 R2上的IIS 7.5上运行。因为升级应用程序会随机崩溃，并导致

503服务不可用响应

。它可以在崩溃前运行几个小时

在崩溃之前，我在事件查看器中收到几个警告，然后是一个错误

警告示例：

A process serving application pool '<My app pool>' terminated unexpectedly. The process id was '14896'. The process exit code was '0x0'.

A process serving application pool '<My app pool>' suffered a fatal communication error with the Windows Process Activation Service. The process id was '18252'. The data field contains the error number.

而且

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: aspnetcore.dll, version: 7.1.1982.0, time stamp: 0x594ab904
Exception code: 0xc0000005
Fault offset: 0x000000000000fe3b
Faulting process id: 0x1ef0
Faulting application start time: 0x01d3622d8eb0e8c0
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\inetsrv\aspnetcore.dll
Report Id: ce37e890-ce20-11e7-9f93-00155dc82c03

---

我真的需要一些帮助才能找到这些崩溃的根源。

Microsoft现在已经更新了ASP.NET Core的IIS模块，这就解决了问题。

是否为IIS安装了aspnetcore模块？如果你在那台机器上运行dotnet，它也会运行吗？是的。该应用程序启动后可以运行数小时，然后突然崩溃。我们也发现了一个类似的错误。到目前为止有什么解决办法吗？我没有。最后生成了一个计划作业，该作业尝试每五分钟启动一次池。您是否有IIS模块更新的引用（如“是否可以安装KB”）？请参阅我在Github上发表的文章中倒数第二条评论。那么，这是.NET Core更新，不是通过KB进行的IIS更新，我读对了吗？谢谢链接。这是对.NET Core的IIS模块的更新，所以不是KB否。

{
  "@t": "2017-11-20T15:24:24.3190000Z",
  "@m": "Request timed out.",
  "@i": "0307d0fb",
  "@l": "Error",
  "@x": "Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Request timed out.\r\n   at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.PipeCompletion.ThrowFailed()\r\n   at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.Pipe.GetResult(ReadResult& result)\r\n   at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.Pipe.Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.IReadableBufferAwaiter.GetResult()\r\n   at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.ReadableBufferAwaitable.GetResult()\r\n   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.MessageBody.<ConsumeAsync>d__24.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Frame`1.<ProcessRequestsAsync>d__2.MoveNext()",
  "SourceContext": "xxxx.Extensions.GlobalExceptionFilter",
  "ActionId": "97118189-7c25-427b-82c7-10b3d885a146",
  "ActionName": "xxxx.Controllers.FileController.Upload (xxxx)",
  "RequestId": "0HL9G4JA0VTIJ:00000073",
  "RequestPath": "/api/file"
}

An unhandled win32 exception occurred in w3wp.exe [18244]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.

Check the documentation index for 'Just-in-time debugging, errors' for more information.

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: aspnetcore.dll, version: 7.1.1982.0, time stamp: 0x594ab904
Exception code: 0xc0000005
Fault offset: 0x000000000000fe3b
Faulting process id: 0x1ef0
Faulting application start time: 0x01d3622d8eb0e8c0
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\inetsrv\aspnetcore.dll
Report Id: ce37e890-ce20-11e7-9f93-00155dc82c03