IIS 5 & IIS 6
Application Pool crash identify bad site
Last post Mar 07, 2008 06:51 AM by Number09
Mar 06, 2008 09:56 AM|Number09|LINK
I am having difficulties with my application pools crashing and hope someone can offer some advise on the best practise for identifying the sites responsible.
This is a shared Windows (2003 Standard SP2) server using IIS 6 to host around 1000 sites, which are a mix of asp.net 1.1, asp.net 2.0, asp, perl and php. I have two main application pools where the .net versions are split and another couple where I quarantine
suspect sites. More often then not the problem is caused by a .net 2.0 site with all sites using the technology hanging and eventually crashing whilst php or html pages still load successfully, an application pool recycle usually clears the problem.
Currently I use Troxio IIS Guide to see the active connections and I have Debug Diagnostics tool to monitor crashes but I cannot make sense of the output from the dump files. I can always see the errors in the Event log and are always similar to this:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event ID: 5000
EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.3959, P3 45d6968e, P4 mscorlib, P5 188.8.131.52, P6 461eee3d, P7 3969, P8 f1, P9 system.invalidoperationexception, P10 NIL.
It's easy enough finding out which application pool but identifying the web site responsible is proving much more difficult, there is no sign of a website ID in the Diag Debug output or in the Event Log. The IIS logs also prove to be of very little help. I
have also tried both IIS Tracer and IIS State but these seem to only work with .net 1.1 but most my customers and problems are with .net 2.0 also installing any ISAPI filters greatly interferes with my logging modules.
I think acquiring this information must be quite common so I must be missing something simple. There must be an easy way to identify troublesome sites either by extracting it from some log or by installing a third party application.
Can anyone shed any light on how to do this or point me in the direction of any software that handles it or even any feedback on how you handle this part of Windows hosting.
Thanks in advance
Mar 06, 2008 03:15 PM|jkmclean|LINK
Sorry can't help you on the monitoring side but perhaps on the crashing side. Have you noticed the handle count going up? If so, it could be AzMan (Microsoft Authorization Manager). We currently have a case open with Microsoft where any AzMan application chews
up memory and handles.
Mar 07, 2008 06:51 AM|Number09|LINK
Thanks for the feedback.
I don't think it is related to Microsoft Authorization Manager but I'll certainly investigate the possibility.
I've added additional reporting in web.config and typically haven't had the issue occur since :) I will update the post with any of my finding since troubleshooting such issues isn't massively documented