MustGather: IBM HTTP Server SSL handshake and configuration problems
 Technote (troubleshooting)
 
Problem(Abstract)
MustGather for SSL handshake and configuration problems with IBM® HTTP Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
 
Resolving the problem
If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for IBM HTTP Server.
Note: Collecting the following MustGather information has been automated in the IBM Support Assistant product feature for WebSphere Application Server. For more information about this automated data collection feature, see Using IBM Support Assistant to collect MustGather data.


SSL handshake and configuration specific MustGather information
The following contains a list of files that are needed for debugging SSL handshake and configuration issues:
  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. Global Security Kit (GSKit) version.

    Type one of the following commands to display the full GSKit version:
    • For Windows:
      • For all releases of V1.3.12:

        /program files/ibm/gsk4/bin/gsk4ver.exe

      • For all releases of V1.3.19, 1.3.26, 2.0.42:

        /program files/ibm/gsk5/bin/gsk5ver.exe

      • For all releases of V1.3.28, 2.0.47, 6.0:

        /program files/ibm/gsk7/bin/gsk7ver.exe

    • For AIX®:
      • For all releases of V1.3.12:

        /usr/opt/ibm/gskit/bin/gsk4ver

      • For all releases of V1.3.19, 1.3.26, 2.0.42:

        /usr/opt/ibm/gskkm/bin/gsk5ver

      • For all releases of V1.3.28, 2.0.47, 6.0:

        /usr/opt/ibm/gskkm/bin/gsk7ver

    • For Solaris™:
      • For all releases of V1.3.12:

        /opt/ibm/gsk4/bin/gsk4ver

      • For all releases of V1.3.19, 1.3.26, 2.0.42:

        /opt/ibm/gsk5/bin/gsk5ver

      • For all releases of V1.3.28, 2.0.47, 6.0:

        /opt/ibm/gsk7/bin/gsk7ver

    • For HP-UX:
      • For all releases of V1.3.12:

        /opt/ibm/gsk4/bin/gsk4ver

      • For all releases of V1.3.19, 1.3.26, 2.0.42:

        /opt/ibm/gsk5/bin/gsk5ver

      • For all releases of V1.3.28, 2.0.47, 6.0:

        /opt/ibm/gsk7/bin/gsk7ver

    • For Linux®:
      • For all releases of V1.3.12:

        /usr/local/ibm/gsk4/bin/gsk4ver

      • For all releases of V1.3.19, 1.3.26, 2.0.42:

        /usr/local/ibm/gsk5/bin/gsk5ver

      • For all releases of V1.3.28, 2.0.47, 6.0:

        /usr/local/ibm/gsk7/bin/gsk7ver

  6. Traces for GSKit and SSL:
    • For IBM HTTP Server standalone:
      1. Stop IBM HTTP Server.
      2. Clear all logs in the install_root/logs directory.
      3. Edit the httpd.conf file:
        1. Change Loglevel to debug.
        2. Add SSLTrace directive to the bottom at the httpd.conf file.
      4. Enable GSKit trace:
        • For Windows:
          1. Create the following system variable:

            GSK_TRACE_FILE

          2. Set the value with the name for the log file; for example: c:\gsktrace.log.
        • For UNIX:
          As the user ID that starts the IBM HTTP Server, create the following environment variable:

          GSK_TRACE_FILE

          You can create the environment variable in either of the two ways:
          • setenv GSK_TRACE_FILE value (full path and filename)

            csh example:

            setenv GSK_TRACE_FILE /usr/HTTPServer/logs/gsktrace_log

            OR

          • export GSK_TRACE_FILE=value (full path and filename)

            ksh example:

            export GSK_TRACE_FILE=/usr/HTTPServer/logs/gsktrace_log

      5. Enable a packet trace on the IBM HTTP Server machine to capture ip traffic between the web server and the client browser. Description of available packet trace tools can be found here... Edge_Component/swg21175744.html
      6. Start IBM HTTP Server.
      7. Recreate the problem.
      8. Capture a netstat -na > netstat.out.
      9. Collect the following data files:
        • httpd.conf, error_log, access_log
        • netstat.out
        • gsktrace_log
        • packet trace
        • key.kdb, key.crl, key.rdb, key.sth (include password)
        • Include the date and time of failure along with the browser version and the full URL that resulted in the SSL failure. For example:

          https: //www.mycompany.com/mystuff/goodies/index.html

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

    • For IBM HTTP Server with WebSphere Application Server:
      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 (Plug-in Trace); for example:

        <Log LogLevel="Trace" Name="/pathto/logs/native.log"/>

      5. Edit the httpd.conf file:
        1. Change Loglevel to debug.
        2. Add SSLTrace directive to the bottom at the httpd.conf file.

      6. Enable GSKit trace:
        • For Windows:
          1. Create a system variable called:

            GSK_TRACE_FILE

          2. Set the value with the name for the log file; for example: c:\gsktrace.log

        • For UNIX:
          As the user ID that starts the IBM HTTP Server, create an environment variable called:

          GSK_TRACE_FILE

          You can create the environment variable in either of two ways:
          • setenv GSK_TRACE_FILE value (full path and filename)

            csh example:

            setenv GSK_TRACE_FILE /usr/HTTPServer/logs/gsktrace_log

            OR

          • export GSK_TRACE_FILE=value (full path and filename)

            ksh example:

            export GSK_TRACE_FILE=/usr/HTTPServer/logs/gsktrace_log

      7. Enable a packet trace on the IBM HTTP Server machine to capture ip traffic between the web server and the client browser. Description of available packet trace tools can be found here... Edge_Component/swg21175744.html
      8. Restart IBM HTTP Server and WebSphere Application Server.
      9. Recreate the problem.
      10. Capture a netstat -na > netstat.out.
      11. Collect the following data files:
        • httpd.conf, error_log, access_log
        • plugin-cfg.xml
        • native.log (V4.0x), http_plugin.log (V5.0x)
        • stderr and stdout
        • netstat.out
        • gsktrace_log
        • packet trace
        • key.kdb, key.crl, key.rdb, key.sth (include password)
        • plugin-key.kdb, plugin-key.sth
        • Include the date and time of failure along with the browser version and the full URL that resulted in the SSL failure. For example:

          https://www.mycompany.com/mystuff/goodies/index.jsp

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

For a listing of all technotes, downloads, and educational materials specific to IBM HTTP Server SSL handshake and configuration issues, 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 > SSL
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1141302
IBM Group: Software Group
Modified date: Mar 30, 2007