☰

IIS 7 应用程序池崩溃如何调试

tag-icon • tag-icon iis-7 application-pools windbg
IIS 7 应用程序池崩溃如何调试

我们在 Windows Server 2012 上配置了多个网站，我们注意到一个网站似乎会间歇性崩溃，而使其恢复在线的唯一方法是重新启动该特定网站，但由于某种原因，回收应用程序池似乎无法帮助该网站恢复在线。有人能告诉我如何诊断这个问题吗？因为我尝试使用调试诊断工具，但找不到问题的根本原因，但这是我使用 !analyze -v 命令收到的异常分析。有人能告诉我如何在生产服务器上诊断这个问题吗？

我们在服务器上看到的实际异常是Autofac.Core.DependencyResolutionException

以下是详细信息windbug

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for PerfMon64.dll - 
Failed calling InternetOpenUrl, GLE=12029

FAULTING_IP: 
+a48e930
00000000`00000000 ??              ???

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  00000000000019f8

PROCESS_NAME:  w3wp.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

MOD_LIST: <ANALYSIS/>

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

MANAGED_STACK: !dumpstack -EE
OS Thread Id: 0x19f8 (0)
Current frame: 
Child-SP         RetAddr          Caller, Callee

BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS_LOG_FILL_PATTERN_ffffffff

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS_LOG_FILL_PATTERN_ffffffff

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_LOG_FILL_PATTERN_ffffffff

LAST_CONTROL_TRANSFER:  from 00007ffdb32a1118 to 00007ffdb5ea079a

STACK_TEXT:  
000000b1`a5e5f598 00007ffd`b32a1118 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!ZwWaitForSingleObject+0xa
000000b1`a5e5f5a0 00007ffd`a3554a52 : 000000b1`a62ba7d0 000000b1`a5e5f6e0 00007ff7`00000000 00000000`000001c0 : KERNELBASE!WaitForSingleObjectEx+0x94
000000b1`a5e5f640 00007ff7`5eff20ca : 00000000`fffffffe 000000b1`a62b6cb0 000000b1`a5e5f780 000000b1`a62b6cb0 : w3wphost!AppHostInitialize+0x152
000000b1`a5e5f680 00007ff7`5eff392d : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : w3wp!wmain+0x40e
000000b1`a5e5f820 00007ffd`b3b313d2 : 00007ff7`5eff39a4 00007ff7`5e38f000 00007ff7`5e38f000 00000000`00000000 : w3wp!ParseCommandLine+0xbd5
000000b1`a5e5f860 00007ffd`b5e254f4 : 00007ffd`b3b313b0 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x22
000000b1`a5e5f890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34


STACK_COMMAND:  ~0s; .ecxr ; kb

FOLLOWUP_IP: 
w3wphost!AppHostInitialize+152
00007ffd`a3554a52 f605ffcb000003  test    byte ptr [w3wphost!g_dwDebugFlags (00007ffd`a3561658)],3

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  w3wphost!AppHostInitialize+152

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: w3wphost

IMAGE_NAME:  w3wphost.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  582757e0

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_LOG_FILL_PATTERN_ffffffff_80000003_w3wphost.dll!AppHostInitialize

BUCKET_ID:  X64_APPLICATION_FAULT_WRONG_SYMBOLS_LOG_FILL_PATTERN_ffffffff_w3wphost!AppHostInitialize+152

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/w3wp_exe/8_5_9600_16384/5215df96/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1

Followup: MachineOwner

谢谢

相关内容