|
Problem |
MustGather for request failure problems with IBM® HTTP
Server. Gathering this information before calling IBM support will help
familiarize you with the troubleshooting process and save you time. |
|
Solution |
If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for IBM HTTP Server.
Request failure specific MustGather information
The following contains a list of files that are needed to debug request
failure problems (for example, 500, 404, 400, etc.).
- Static Content (.html, .gif, .jpeg, and so
on)
- IBM HTTP Server version.
Type one of the following commands to display the full IBM HTTP
Server version:
- For Windows®:
- For all releases of V1.3.12, 1.3.19, 1.3.26, 1.3.28,
2.0.42, 2.0.47, 6.0:
- For UNIX®:
- For all releases of V1.3.12, 1.3.19, 1.3.26, 1.3.28:
install_root/bin/httpd
-ver |
|
- For all releases of V2.0.42, 2.0.47, 6.0:
install_root/bin/apachectl -V |
|
- Configuration file:
install_root/conf/httpd.conf |
|
- Error log:
- For Windows:
install_root/logs/error.log |
|
- For UNIX:
install_root/logs/error_log |
|
- Access log:
- For Windows:
install_root/logs/access.log |
|
- For UNIX:
install_root/logs/access_log |
|
- Debug:
- Stop IBM HTTP Server.
- Clear all logs in the install_root/logs
directory.
- Edit the httpd.conf file and change Loglevel to
debug.
- Restart IBM HTTP Server.
- Recreate the failure.
- Collect the following data files and information:
- httpd.conf
- error_log
- access_log
- IBM HTTP Server version
- The date and time of failure
- The browser version
- The full URL that resulted in failure. For example:
http://www.mycompany.com/mystuff/index.html |
|
- Follow instructions to send
diagnostic information to IBM support.
- Dynamic Content (Servlet, JSP, and so on)
- IBM HTTP Server version.
Type one of the following commands to display the full IBM HTTP Server
version:
- For Windows:
- For all releases of V1.3.12, 1.3.19, 1.3.26, 1.3.28,
2.0.42, 2.0.47, 6.0:
- For UNIX:
- For all releases of V1.3.12, 1.3.19, 1.3.26, 1.3.28:
install_root/bin/httpd
-ver |
|
- For all releases of V2.0.42, 2.0.47, 6.0:
install_root/bin/apachectl -V |
|
- Configuration file:
install_root/conf/httpd.conf |
|
- Error log:
- For Windows:
install_root/logs/error.log |
|
- For UNIX:
install_root/logs/error_log |
|
- Access log:
- For Windows:
install_root/logs/access.log |
|
- For UNIX:
install_root/logs/access_log |
|
- Traces: IBM HTTP Server<-->WebSphere Application Server V4.0,
V5.0, V5.1, and V6.0.
- Stop IBM HTTP Server and WebSphere Application Server.
- Clear all logs in the IBM HTTP Server directory:
- Clear all logs in the WebSphere Application Server directory:
- Edit the plugin-cfg.xml file and change Loglevel to
Trace. For example:
<Log LogLevel="Trace"
Name="c:\WebSphere\AppServer\logs\native.log"/> |
|
- Edit the httpd.conf file and change Loglevel to
debug.
- On the Application Server, set the following trace string:
- Websphere Application Server V6.0
- In the Administrative Console, expand the Troubleshooting section and
click Logs and Trace.
- Click on your server.
- Click Change Log Detail Levels.
- In Trace Specification, enter the following trace string:
*=info:com.ibm.ws.webcontainer.*=all:com.ibm.wsspi.webcontainer.*=all:HTTPChannel=all:GenericBNF=all |
|
- For Trace Output, choose File and type a filename.
- Click Apply and save your configuration.
- WebSphere Application Server V5.0 and 5.1
- In the Administrative Console, expand the Troubleshooting section and
click Logs and Trace.
- Click on your server.
- Click Diagnostic Trace.
- In Trace Specification, enter the following trace string:
Servlet_Engine=all=enabled:HTTP_Transport=all=enabled |
|
- For Trace Output, choose File and type a filename.
- Click Apply and save your configuration.
- WebSphere Application Server V4.0
- In the administrative client, select the Application Server in the
topology tree.
- Go to the Services tab and select Trace Service, then Edit
properties.
- In the Trace Service window, specify the trace string:
com.ibm.ws.http*=all=enabled |
|
- In the Trace Service window, specify also the output file with
the fully-qualified path.
- Click OK in the Trace Service window.
- Click Apply.
- Restart IBM HTTP Server and WebSphere Application Server.
- Recreate the failure.
- Collect the following data files and information for review:
- httpd.conf
- error_log
- access_log
- plugin-cfg.xml
- For releases of V5.0, V5.1, V6.0:
http_plugin.log
- For releases of V4.0: native.log
- stderr and stdout
- TraceFile (From Step 5)
- IBM HTTP Server version
- The date and time of failure
- The browser version
- The full URL that resulted in failure. For example:
http://www.mycompany.com/mystuff/index.html |
|
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to IBM HTTP Server request failure problems, search the IBM
HTTP Server support site. |
|
|