RE: iis crash/hang agent
From: scottrm (scottrm123_at_nospam.com)
Date: 02/02/04
- Next message: SGSM: "Understanding IIS Logs"
- Previous message: JRL: "CDO - uuencoded attachment corrupted."
- Next in thread: Stefan Schachner[MSFT]: "RE: iis crash/hang agent"
- Reply: Stefan Schachner[MSFT]: "RE: iis crash/hang agent"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 2 Feb 2004 03:21:06 -0800
I have configured the iischagent.ini file according to your instructions. When I tried it on my development server it seemed to work ok as I got a message in the event log after I restarted iis saying that both the hang agent and crash agent are enabled. However on the live server I get the following message in the event log indicating the hang agent is not enabled.
The service was started.
IISCrashHangAgent Settings:
Crash agent only is enabled.
Debug level: 0.
I am using an identical iischagent.ini file on both servers and they are both the same operating system, windows 2003. A copy of the iischagent.ini file can be found below, any ideas on what is going wrong?
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;
;;; Copyright (c) 2003 Microsoft Corporation. All rights reserved.
;;;
;;; IIS Crash and Hang Monitoring Agent. Version 1.1
;;;
;;; OVERVIEW:
;;;
;;; This INI file is the configuration file for the IISCHAgent.dll and
;;; _IISCHAgent.exe modules. The purpose of this tool is to monitor
;;; IIS for a crash (unexpected process exit) of inetinfo.exe and/or for a hang
;;; which is represented by a request that takes too long to complete. In the
;;; case of a crash, a log file containing the requests that are in flight will
;;; written to the LogLocation directory. An event will be logged in the
;;; Application Event Log. In the case of a hang, the agent can write a log file
;;; containing the request that is 'hung', and the requests in flight. It can
;;; also launch an ActionCommand.
;;;
;;;
;;; MANUAL INSTALATION:
;;;
;;; 1. Place the files in the same directory together. For example:
;;; C:\IISDebugTools
;;;
;;; 2. Configure this ini file using the options in the CrashAgent and/or
;;; HangAgent sections bellow.
;;;
;;; 3. Configure the IISCHAgent.dll as a global filter in IIS by running
;;; the following command:
;;;
;;; _IISCHAgent.exe /i. Then restart IIS. For example:
;;; > _IISCHAgent.exe /i
;;; > iisreset /restart
;;;
;;; If the /i fails, you can follow these steps to manually install the filter:
;;;
;;; Open the Internet Information Services MMC snap-in and right
;;; click the computer icon and choose properties. Click the Edit button
;;; for the WWW Service Master Properties. Choose the ISAPI filters tab. Click
;;; Add and enter "IISCrashHangAgent" for the filter name,
;;; and browse to the IISCHAgent.dll and click ok.
;;; Click on in the WWW Service Master Properties dialog, and
;;; click ok in the computer Properties dialog. Right click the computer icon
;;; and choose Restart IIS. Once restarted, return to the global filters list
;;; and highlight the IISCrashHangAgent filter in the list. Click the up arrow
;;; button until the IISCrashHangAgent filter is above all other filters.
;;; Then restart IIS again using the Restart IIS option.
;;;
;;;
;;; MANUAL UNINSTALL:
;;;
;;; 1. Run _IISCHAgent.exe /u. Then restart IIS.
;;; 2. Delete the directory or just the files.
;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;
;;; CrashAgent Options
;;;
;;; Enable: Specifies whether to run the CrashAgent part of the tool.
;;; The default is 1 (enabled).
;;;
;;; LogLocation: Specifies where to write the CrashAgent log files to.
;;; The directory will be created if it doesn't exist. The
;;; default is "logs" under the installation directory.
;;;
;;; MaxLogFiles: Specifies the maximum number of CrashAgent logs to keep.
;;; The default is 10.
;;;
;;; PreActionCommand: Specifies a command to be executed when the CrashAgent
;;; first initializes. This can be used to attach a debugger,
;;; such as iisdump, to the IIS process at startup. %d is
;;; supported to send the process id of the IIS process.
;;; The command is executed each time _iischagent.exe is
;;; started, and the CrashAgent is enabled.
;;; An example using IISDump:
;;;
;;; iisdump.exe -d -i -p %d
;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[CrashAgent]
Enable=1
LogLocation=C:\iisdebugtools\logs
;MaxLogFiles=10
PreActionCommand=iisdump.exe -d -i -p %d
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;
;;; HangAgent Options
;;;
;;; Enable: Specifies whether to run the HangAgent part of the tool.
;;; The default is 0 (disabled). If enabled, RequestTimeLimit
;;; must be specified, and one or both of WriteLog and
;;; ActionCommand+MaxActionsAllowed must be specified.
;;;
;;; LogLocation: Specifies where to write the HangAgent log files to.
;;; The directory will be created if it doesn't exist. The
;;; default is "logs" under the installation directory.
;;;
;;; MaxLogFiles: Specifies the maximum number of HangAgent logs to keep.
;;; The default is 10.
;;;
;;; WriteLog: Specifies whether to write a HangAgent log file or not.
;;; Default is 1 (on). If this is disabled, then
;;; ActionCommand and MaxActionsAllowed must be specified.
;;;
;;; RequestTimeLimit: Specifies the time limit for determining when a request
;;; has taken too long. There is no default. This must be
;;; specified to enable the HangAgent.
;;;
;;; ActionCommand: Specifies an optional action to take when a request
;;; has exceeded the RequestTimeLimit. The process id of
;;; inetinfo can be obtained using %d. The log entry for
;;; the request that took to long can be obtained by
;;; using %s. Only %d and %s are allowed. No other '%'
;;; options are valid. The %d and %s can be in any order.
;;; (NOTES: only one (1) ActionCommand may be specified.
;;; Paths to executables with spaces in them must have
;;; the path to executable quoted.
;;; IE: "c:\program files\Tools\mytool.exe" /switch )
;;;
;;; Some examples of what ActionCommand can be:
;;;
;ActionCommand=iisreset /restart
;ActionCommand=C:\IISDebugTools\iisdump.exe
;ActionCommand=cscript.exe "c:\Program Files\Debuggers\adplus.vbs" -hang -iis -quiet -o c:\logs
;ActionCommand=net send localhost Process %d had a request take too long: %s
;;;
;;; MaxActionsAllowed: Specifies the maximum number of times to execute
;;; the ActionCommand. The default is 0 (no actions).
;;; must be set to non-zero for any Action to be taken.
;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[HangAgent]
Enable=1
LogLocation=C:\iisdebugtools\logs
;MaxLogFiles=10
WriteLog=1
RequestTimeLimit=5
ActionCommand=C:\IISDebugTools\iisdump.exe
MaxActionsAllowed=1
- Next message: SGSM: "Understanding IIS Logs"
- Previous message: JRL: "CDO - uuencoded attachment corrupted."
- Next in thread: Stefan Schachner[MSFT]: "RE: iis crash/hang agent"
- Reply: Stefan Schachner[MSFT]: "RE: iis crash/hang agent"
- Messages sorted by: [ date ] [ thread ]