Collecting Generic Directory Proxy Server Data

No matter the type of problem you are encountering, there is a minimum set of data that needs to be collected and, if necessary, provided to Sun Support.

Collecting Version Information for Directory Proxy Server

The following sections describe how to collect configuration information on current and previous versions of Directory Proxy Server.

Collecting Directory Proxy Server 6.2 Version Information

Collect the Directory Proxy Server 6.2 version information. This information is available in the instance-dir/logs/error file. For example, the error log displays the version information as follows:

[21/May/2007:18:01:27 +0200] - STARTUP    - INFO  - \
Sun-Java(tm)-System-Directory-Proxy-Server/6.1 B2007.134.2156 started \
on host server1 in directory /local/dps.3333

Collecting Directory Proxy Server 5.x Version Information

If you are using migrated Directory Proxy Server 5.x instances, collect the version information as follows:

# install-path/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 this error, set the 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=install-path/lib

Running the dpadm Command in Verbose Mode

Running the dpadm command in verbose mode will provide information to help troubleshoot problems that occur during instance creation or deletion, data backup, and so on. Run the dpadm is verbose mode as follows:

# dpadm -v

Collecting Directory Proxy Server Configuration Information

The following sections describe how to collect configuration information on current and previous versions of Directory Proxy Server.

Collecting Configuration Information on Directory Proxy Server 6.2

Collect the Directory Proxy Server 6.2 configuration information. This information is available in the instance-dir/logs/error file. For example, the error log displays the configuration information as follows:

user@server1 local]$ more dps.3333/logs/errors
[21/May/2007:18:01:27 +0200] - STARTUP    - INFO  - Global log level INFO (from config)
[21/May/2007:18:01:27 +0200] - STARTUP    - INFO  - Logging Service configured
[21/May/2007:18:01:27 +0200] - STARTUP    - INFO  - Java Version: 1.5.0_09 (Java Home: \
/local/jre)
[21/May/2007:18:01:27 +0200] - STARTUP    - INFO  - Java Heap Space: Total Memory (-Xms) \
= 246MB, Max Memory (-Xmx) = 246MB
[21/May/2007:18:01:27 +0200] - STARTUP    - INFO  - Operating System: \
Linux/i386 2.6.17-1.2139_FC5smp

Collecting Configuration Information on Directory Proxy Server 5.x

Collect the Directory Proxy Server 5.x configuration information as follows:

# cd install-path/bin/dps_utilities
# ./dpsconfig2ldif -t install-path/dps-name/etc/tailor.txt.backup \
-o /tmp/DPS_tailor_Config.ldif

The DPS_tailor_Config.ldif file contains configuration information formatted as follows:

Begin configuration_url:file:///server-root/instance/
etc/tailor.ldif#cn=dps-instance1,cn=Sun ONE Directory Proxy Server,
cn=ServerGroup (1),cn=instance1.example.com,ou=example.com,
o=NetscapeRoot End

Collecting Directory Proxy Server Log Information

Collect the Directory Proxy Server logs. By default, the logs are stored in the following directory:

instance-path/logs

If you are providing this information to Sun Support, you should also include the generic Directory Server data from the various Directory Servers involved. This generic data includes the Directory Server version and the Directory Server access, error, and audit logs. For more information about collecting the Directory Server generic information, see Collecting Generic Data.

Include generic information about any other backend servers you may be using, such as JDBC backends, a SQL database, or an Oracle database.