Collecting data for problems with the IBM® HTTP Server for LDAP authentication problems. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.
Collecting data for problems with the IBM® HTTP Server for LDAP authentication problems. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.
If you have already contacted support, continue to the component-specific MustGather information. Otherwise, click: MustGather: Read first for IBM HTTP Server.
LDAP authentication specific MustGather information
The following list of files are needed for debugging two types of LDAP authentication with IBM HTTP Server:
- LDAP authentication over non-Secure Socket Layers (SSL)
- LDAP authentication over SSL
1. LDAP authentication over non-Secure Socket Layers (SSL)
- IBM HTTP Server version.
Type one of the following commands to display the full version:
- For Windows®:
- For UNIX®:
| 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 |
|
- LDAP properties file:
| install_root/conf/ldap.prop |
|
Traces: IBM HTTP Server LDAP (non-SSL)
- Stop IBM HTTP Server.
- Clear all logs in the install_root/logs directory.
- Edit the httpd.conf file. Change Loglevel to debug.
- Enable LDAP tracing:
- For Windows:
- Create a system variable called:
- Set the value with the name for the log file (for example: c:\ldaptrace.log).
- Create a system variable called:
- Set the value to 65535.
- For UNIX:
- As the user ID that starts the IBM HTTP Server, create an environment variable called:
| LDAP_TRACE_FILE |
The environment variable can be created in either of these two ways:
- setenv LDAP_TRACE_FILE value (full path and filename)
csh example:
| setenv LDAP_TRACE_FILE /usr/HTTPServer/logs/ldaptrace_log |
OR
|
- export LDAP_TRACE_FILE=value (full path and filename)
ksh example:
| export LDAP_TRACE_FILE=/usr/HTTPServer/logs/ldaptrace_log |
|
|
- As the user ID that starts the IBM HTTP Server, create an environment variable called:
| LDAP_DEBUG |
The environment variable can be created in either of these two ways:
- csh example:
| setenv LDAP_DEBUG=65535 |
OR
|
- ksh example:
|
- Start IBM HTTP Server.
- Recreate the problem.
- Capture the following:
| netstat -na > netstat.out |
|
a. Collect the following data files:
- httpd.conf, error_log, access_log
- netstat.out
- ldaptrace_log
- ldap.prop
- IBM HTTP Server version output
- Include the date and time of failure along with the browser version and the full URL that resulted in the LDAP failure. For example:
b. Follow instructions to send diagnostic information to IBM support.
2. LDAP over SSL
- IBM HTTP Server version.
Type one of the following commands to display the full version:
- For Windows:
- For UNIX:
| 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 |
|
- LDAP properties file:
| install_root/conf/ldap.prop |
|
Traces: IBM HTTP Server LDAP over SSL
- Stop IBM HTTP Server.
- Clear all logs in the install_root/logs directory.
- Edit the httpd.conf file:
- Change Loglevel to debug.
- Add SSLTrace directive to the bottom of the httpd.conf file.
- Enable LDAP tracing:
- For Windows:
- Create the following system variable:
- Set the value with the name for the log file (for example: c:\ldaptrace.log).
- Create the following system variable:
- Set the value to 65535.
- For UNIX:
- As the user ID that starts the IBM HTTP Server, create an environment variable called:
| LDAP_TRACE_FILE |
The environment variable can be created in either of the two ways:
- setenv LDAP_TRACE_FILE value (full path and filename)
csh example:
| setenv LDAP_TRACE_FILE /usr/HTTPServer/logs/ldaptrace_log |
OR
|
- export LDAP_TRACE_FILE=value (full path and filename)
ksh example:
| export LDAP_TRACE_FILE=/usr/HTTPServer/logs/ldaptrace_log |
|
|
- As the user ID that starts the IBM HTTP Server, create an environment variable called:
| LDAP_DEBUG |
The environment variable can be created in either of the two ways:
- csh example:
| setenv LDAP_DEBUG=65535 |
OR
|
- ksh example:
|
- Enable GSKit trace:
- For Windows:
- Create the following system variable:
- 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. |
The environment variable can be created 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 |
|
|
- Start IBM HTTP Server.
- Recreate the problem.
- Capture the following:
| netstat -na > netstat.out |
|
a. Collect the following data files:
- httpd.conf, error_log, access_log
- netstat.out
- ldaptrace_log
- gsktrace_log
- ldap.prop
- IBM HTTP Server version
- Include the date and time of failure along with the browser version and the full URL that resulted in the LDAP failure. For example:
b. Follow instructions to send diagnostic information to IBM support.
[{"Product":{"code":"SSEQTJ","label":"IBM HTTP Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Security (LDAP- Authentication- etc.)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.5;8.0;7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"IBM HTTP Server","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]