The Dr. Watson tool supplied with Windows must be configured to save information about program crashes. This setup step must be performed prior to the crash.
These steps must be performed after the crash occurs.
Save the Dr. Watson log and crash files. These are in the locations configured in the DRWTSN32.EXE program, as displayed above under System preparation. Example:
C:\Documents and Settings\All Users\Documents\DrWatson>dir Volume in drive C is C_Drive Volume Serial Number is 98E7-6D3C Directory of C:\Documents and Settings\All Users\Documents\DrWatson 08/05/2003 09:32a <DIR> . 08/05/2003 09:32a <DIR> .. 04/05/2005 03:48p 1,118,951 drwtsn32.log 04/05/2005 03:49p 12,969,444 user.dmp 2 File(s) 14,088,395 bytes 2 Dir(s) 18,162,450,432 bytes free
The files drwtsn32.log and user.dmp are the files to save.
Use the System and web server
information tool to gather this information. This will result in
a directory of information called
ServerConfig.timestamp
, which should then be
zipped.
The default file is
install_root\conf\httpd.conf
The default file is
install_root\logs\error.log
The configuration file may have been changed to specify a different error log.
The actual location is specified in plugin-cfg.xml
and
is generated by configuring LogLevel="Trace"
.
Example:
c:\WebSphere\AppServer\logs\http_plugin.log
Run Start/Programs/Accessories/System Tools/System Information, highlight the top level "System Information" selection, right mouse click, select "Save as Text File", enger "system_info" for the filename to save as, and then "Save" (this may take a few minutes):
ServerConfig.timestamp
directory
system_info.txt
by the System Information program
In order to identify a known crash from drwtsn32.log, first open the log file in a text editor, e.g. notepad.exe. Move to the bottom of the file, then select Edit/Find, check Match-case, select Direction-Up, and enter the Find-what text "FAULT" (do not include the quotes).
Known crashes can be identified by looking for the text indicated below. It will be either close to the FAULT pointer or in the Function Name of the Stack Back Trace just below the FAULT pointer.
Search text | Problem Resolution |
---|---|
ap_die | IHS 2.0.42.2: Fixed in APAR PQ85834
IHS 2.0.47: Fixed in IHS 2.0.47.1 |
gsk_attribute_get_data | Fixed in mod_ibm_ssl (not GSKit) at current recommended service levels
In theory could happen on other platforms but so far the crash has only been seen on Windows |
gsk_attribute_get_cert_info | FPK59158, fixed in Plugin 6.1.0.17 and later |
mod_ibm_ssl!updateLibpath | PK91197 (IHS 6.0 and 6.1 only) |
Certain third party software may add a Winsock Service Provider layer which sits between IHS and the TCP/IP network. If this software does not implement some of the Microsoft advanced Winsock functions correctly, such as AcceptEx, it may cause IHS to crash on startup or restart. A possible fix is to add the "Win32DisableAcceptEx" directive to the IHS configuration file. Setting "MaxRequestsPerChild 0" (the recommended default) may also eliminate the crashes. This crash may be accompanied by the following message in the error log:
[warn] (OS 10038)An operation was attempted on something that is not a socket. : setsockopt(SO_UPDATE_ACCEPT_CONTEXT) failed.