1.5.3 To Collect Required Debug Data for Directory Editor Startup Problems

This section describes what data to collect when you cannot start Directory Editor.

1. Collect information about the port used for your application server.

   UNIX and Linux

   netstat -an | grep app-server-port

   Windows

   netstat -an

2. Collect error logs for your application server.

   For example, if you run Directory Editor in the first domain and instance of Sun Java System Application Server, collect app-server-root/domains/domain1/server1/logs/server.log.

3. Collect logs from both the Directory Editor Configuration Directory Server and also Managed Directory Servers.

   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.

4. Collect the de-startup-problem-services.ldif file generated by the ldapsearch command.

   Be sure to include the -B option, which retrieves binary attribute values as they are stored in the directory.

   UNIX and Linux

   server-root/shared/bin/ldapsearch -h hostname -p port -D "cn=Directory Manager" -w password -B -b "ou=1.0,ou=DML,ou=services,dc-root" "(objectclass=*)" > /tmp/de-startup-problem-services.ldif

   Windows

   server-root\shared\bin\ldapsearch.exe -h hostname -p port -D "cn=Directory Manager" -w password -B -b "ou=1.0,ou=DML,ou=services,dc-root" "(objectclass=*)" > C:\de-startup-problem-services.ldif

   Here, dc-root means the domain controller suffix for the configuration directory used in your environment, such as dc=example,dc=com.