Directory Proxy Server

Recommended Data Collection for Directory Proxy Server Issues:

When contacting Sun Support to obtain assistance with a Directory Proxy Server issue, it is necessary to provide a detailed problem description and a minimum set of required data - directly below are some guidelines on these topics. It may also be necessary to collect additional data which is more specific to the problem - recommendations for which will follow in later sections.

Required Information:

• A clear current detailed problem description
• Current dateline of the DPS state, before and after the problem started, including actions already attempted.
• List of any changes that took place up to the current time, including changes that took place prior to the problem taking place.
• Complete network topology that includes host names, assigned IPs, OS versions, network hardware , software versions and location preferred in graphical format.
• Is this issue in a development, test or production environment?
• If production, is a development or test environment available?
• Is the problem continuous, or reproducible? If so please provide a complete step by step test case including sample data.
• Sun Explorer (SUNWexplo) output for the host where the issue took place.
• Was DPS installed using the Sun Package version or the zip install?

• Provide the DPS configuration

To dump the DPS configuration data please do the following:
DPS 5.x: /server-root/bin/dps_utilities/dpsconfig2ldif -t /server-root/dps-hostname/etc/tailor.txt -o /tmp/dps-config.ldif
DPS 6.x: /instance-path/config/conf.ldif

• Provide the complete Directory Proxy Server version

To determine the version information please do the following.
DPS 5.x: /server-root/bin/dps/server/bin/ldapfwd -v
DPS 6.x: /install-path/dps6/bin/dpadm -V instance-path

You can also confirm the version using the errors log located in the instance-path/logs directory.
It can be located by searching for "STARTUP" and looking for the "INFO" line that explains when the instance started.

• Provide DPS log files

The logs can be found in this location
DPS 5.x: /server-root/dps-hostname/logs/fwd.log
DPS 6.x: /instance-path/logs/access
/instance-path/logs/errors

• Provide Sun Directory Server backend log files. If using any another LDAPV3 complaint LDAP directory please reference the manufactures documents to find how to enable and collect the logs.

The logs can be found in this location
SunDS5: /server-root/slapd-instance_name/logs/error
/server-root/slapd-instance_name/logs/access
/server-root/slapd-instance_name/logs/audit (If Audit logging is enabled)
SunDS6: /instance-path/logs/access
/instance-path/logs/errors
/instance-path/logs/audit (If Audit logging is enabled)

If the logs do not exist in their default locations, examine the Directory Server configuration file, (SunDS6) instance-path/config/dse.ldif, (SunDS5) /server-root/slapd-instance_name/config/dse.ldif, to find the paths to the log files. The attributes that disclose the location to the files are nsslapd-accesslog, nsslapd-errorlog and nsslapd-auditlog (If enabled).

You can also use a script called Dirtracer from here to collect the SunDS data, which would cover all the requested data for the directory server.
You can find the script located at, "http://www.sun.com/bigadmin/scripts/indexSjs.html"

• If using a SunDS LDAP backend(s), please provide the version of the directory server(s).
  To find this data you can do the following.
  SunDS5: cd /server-root/bin/slapd/server then ./ns-slapd -D /server-root/slapd-instance_name -V
  SunDS6: /install-path/lib/ns-slapd -D instance-path _V

-

Using Java Tools with the Directory Proxy Server:

The Directory Proxy Server version 6.X is a 100% Java application. This means you can use the standard java tools that are delivered with the JDK 1.5 to help troubleshoot problems.
The common tools included with the JDK are the following:
jstack : Information about the thread stack
jstat : JVM performance statistics
jinfo : JVM environment information
jmap : Memory information which can include the histogram of the heap
jconsole : A graphical tool to provide information on memory usage, threads in use, and the JVM parameters that are defined.

In Solaris these tools can be found in the, /usr/jdk/latest/bin directory.

On a Unix platform you can use, kill -QUIT process_id , command to produce a thread dump. If this does not work you can use jstack. If on Solaris 10 you can also use the pstack command as it now also displays Java frames.

For Further Information:

Please see Java Self Help for more information on Java debugging.
http://wikis.sun.com/display/SoftwareSupport/Sun+Microsystems+Software+Support#SunMicrosystemsSoftwareSupport-JavaSelfhelp
External documents for troubleshooting can be found at, http://docs.sun.com/app/docs/doc/820-2768/proxy?l=en&a=view
To collect the required debug data for most Directory Proxy Server problems can be found at, http://docs.sun.com/app/docs/doc/820-0436.