MustGather: Request failure (500, 404, 400, etc.) problems
 Technote (FAQ)
 
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

Do you want to automate the collection of MustGather data?
Collecting the following MustGather information has now been automated in the IBM Support Assistant. For more information about automating data collection, see Using IBM Support Assistant to collect MustGather data.

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)
    1. 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:

          install_root/apache -v

      • 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

    2. Configuration file:

      install_root/conf/httpd.conf

    3. Error log:
      • For Windows:

        install_root/logs/error.log

      • For UNIX:

        install_root/logs/error_log

    4. Access log:
      • For Windows:

        install_root/logs/access.log

      • For UNIX:

        install_root/logs/access_log

    5. Debug:
      1. Stop IBM HTTP Server.
      2. Clear all logs in the install_root/logs directory.
      3. Edit the httpd.conf file and change Loglevel to debug.
      4. Restart IBM HTTP Server.
      5. Recreate the failure.

    6. 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

    7. Follow instructions to send diagnostic information to IBM support.

  • Dynamic Content (Servlet, JSP, and so on)
    1. 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:

          install_root/apache -v

      • 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

    2. Configuration file:

      install_root/conf/httpd.conf

    3. Error log:
      • For Windows:

        install_root/logs/error.log

      • For UNIX:

        install_root/logs/error_log

    4. Access log:
      • For Windows:

        install_root/logs/access.log

      • For UNIX:

        install_root/logs/access_log

    5. Traces: IBM HTTP Server<-->WebSphere Application Server V4.0, V5.0, V5.1, and V6.0.
      1. Stop IBM HTTP Server and WebSphere Application Server.

      2. Clear all logs in the IBM HTTP Server directory:

        install_root/logs

      3. Clear all logs in the WebSphere Application Server directory:

        install_root/logs

      4. Edit the plugin-cfg.xml file and change Loglevel to Trace. For example:

        <Log LogLevel="Trace" Name="c:\WebSphere\AppServer\logs\native.log"/>

      5. Edit the httpd.conf file and change Loglevel to debug.

      6. On the Application Server, set the following trace string:
        • Websphere Application Server V6.0
          1. In the Administrative Console, expand the Troubleshooting section and click Logs and Trace.

          2. Click on your server.

          3. Click Change Log Detail Levels.

          4. In Trace Specification, enter the following trace string:

            *=info:com.ibm.ws.webcontainer.*=all:com.ibm.wsspi.webcontainer.*=all:HTTPChannel=all:GenericBNF=all

          5. For Trace Output, choose File and type a filename.

          6. Click Apply and save your configuration.

        • WebSphere Application Server V5.0 and 5.1
          1. In the Administrative Console, expand the Troubleshooting section and click Logs and Trace.

          2. Click on your server.

          3. Click Diagnostic Trace.

          4. In Trace Specification, enter the following trace string:

            Servlet_Engine=all=enabled:HTTP_Transport=all=enabled

          5. For Trace Output, choose File and type a filename.

          6. Click Apply and save your configuration.

        • WebSphere Application Server V4.0
          1. In the administrative client, select the Application Server in the topology tree.

          2. Go to the Services tab and select Trace Service, then Edit properties.

          3. In the Trace Service window, specify the trace string:

            com.ibm.ws.http*=all=enabled

          4. In the Trace Service window, specify also the output file with the fully-qualified path.

          5. Click OK in the Trace Service window.

          6. Click Apply.

      7. Restart IBM HTTP Server and WebSphere Application Server.

      8. Recreate the failure.

    6. 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

    7. 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.
 
Related information
Submitting information to IBM support
Steps to getting support
MustGather: Read first
Troubleshooting guide
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server IBM HTTP Server
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > IBM HTTP Server > Base Server
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1141306
IBM Group: Software Group
Modified date: Apr 14, 2007