To Collect Required Debug Data For Any Directory Proxy Server Problem

All problems described in this technical note need basic information collected about when the problem occurred and about the system having the problem. Use this task to collect that basic information.

1. Note the time or times the problem occurred.

2. If possible, collect explorer output from SUNWexplo software on the system where the problem occurred.

3. Provide graphical representation of your deployment.

   The graphical representation of your deployment is key to understanding the context of the problem. Show the following in the graphical representation.

   • All computers involved, with their IP addresses, hostnames, roles in the deployment, operating systems, and versions used.

   • All other relevant systems, including load balancers, firewalls, and so forth.

4. Note the operating system version.

   Solaris OS

   uname -a

   HP-UX

   uname -r

   Red Hat

   cat /etc/redhat-release

   Windows

   C:\Program Files\Common files\Microsoft Shared\MSInfo\msinfo32.exe /report C:\report.txt

5. Note the patch level.

   Solaris OS

   showrev -p

   HP-UX

   swlist

   Red Hat

   rpm -qa

   Windows

   Already provided in C:\report.txt.

6. Note the version of Directory Proxy Server.

7. To determine the version information, use the ldapfwd -v command.

   server-root/bin/dps/server/bin/ldapfwd -v

   On UNIX and Linux systems, you might see the following error.

   ld.so.1: ldapfwd: fatal: libnss3.so: open failed: No such file or directory

   If you see the error, set LD_LIBRARY_PATH to include Directory Proxy Server libraries in your load path. For example, if you use sh, use the following command.

   export LD_LIBRARY_PATH=server-root/lib

8. Collect the Directory Proxy Server configuration file generated with the dpsconfig2ldif command.

   UNIX and Linux

   server-root/bin/dps_utilities/dpsconfig2ldif -t server-root/dps-serverID/etc/tailor.txt -o /tmp/config.ldif

   Windows

   server-root\bin\dps_utilities\dpsconfig2ldif -t server-root\dps-serverID\etc\tailor.txt -o %TEMP%\config.ldif

9. Collect Directory Proxy Server trace logging information.

   1. Access the Directory Proxy Server Console.

   2. Select the Configuration tab.

   3. Select the Logs node.

   4. In the Log detail drop-down list, select Detailed trace.

   5. Save your work.

   6. Restart Directory Proxy Server.

   7. After reproducing the problem, collect the server-root/dps-serverID/logs/fwd.log file.

10. Collect Directory Server version information with the nsslapd -V command for directories accessed through the proxy.

    server-root/bin/slapd/server/ns-slapd -D instance-dir -V

11. Collect Directory Server access, errors, and audit logs for directories accessed through the proxy.

    When you find more than one log file of each type, collect each of the log files. If possible, provide logs that show server operation before the problem occurred, and also logs written as the problem occurred.

    By default, you find these logs in the following locations.

    server-root/slapd-serverID/logs/access

    server-root/slapd-serverID/logs/errors

    server-root/slapd-serverID/logs/audit (if enabled)

    If these log files are not in the default locations, examine the Directory Server configuration file, server-root/slapd-serverID/config/dse.ldif, to find the paths to the logs. The paths are specified as the values of attributes nsslapd-accesslog, nsslapd-errorlog, and nsslapd-auditlog.