mod_whatkilledus for IHS 2.0 writes information about the current connection and request to the error log after an IHS child process crash. This provides important information for interpreting a core dump, and even without a core dump it can be used to determine what types of requests lead to crashes. (Is the connection leading to a crash always to an SSL port? Is the request leading to a crash always for an object handled by a certain plug-in module? Is the connection leading to a crash always from the same client?)
Any installation of IHS 2.0.42.2 or above on AIX, Linux, Solaris, or HP-UX should have this module installed and activated.
(Note: The version of this module for IHS 1.3 is described here.)
Copy mod_whatkilledus.so for your platform to the modules directory in the web server installation location (e.g., to /opt/IBMIHS/modules).
Add the following directive after existing LoadModule directives:
LoadModule whatkilledus_module modules/mod_whatkilledus.so
Restart the server so that the updated configuration takes effect.
After requests are received, but before most plug-in modules run, the module saves information about the request in case the child process crashes while processing that request. This introduces a small amount of overhead into request processing, but the overhead is hard to measure and certainly is not noticeable.
Comment out the LoadModule
directive added as part of the activation step.
Restart the server so that the updated configuration takes effect.