Collecting and Analyzing 5.x Console Data

This section describes how to collect and then analyze data about failures with the 5.x Directory Server console.

The console may fail for one of the following reasons:

• Directory Server not running

• The user that is logged in is missing rights

• Wrong jar files

• Wrong version of Java

Collecting 5.x Console Troubleshooting Data

1. Verify that the Admin Server is running.

   # ps -ef | grep httpd

   If yes, proceed to the next step.

2. Verify that Directory Server is running.

   # ps -ef | grep slapd

   If yes, proceed to the next step.

3. Collect the Admin Server logs.

4. Launch the startconsole command in debugging mode as follows:

   # ./startconsole -D 9:all -f /tmp/console_trace

   Now reproduce the problem. Check the console_trace file output by the startconsole command for errors, such as the Java version, paths to loaded jar files, Java exceptions.

5. Match the exceptions in the console_trace file with the contents of the errors log.

Analyzing the Console Data

If you are using a 5.2 version of the Console, confirm that the correct jar files are being used.

Next, determine if a 5.1 installation of the Console existed previous to your installation of the 5.2 version. You can make this verification by running startconsole as follows:

# ./startconsole -D

If running this command does not work, use the following instead:

# /usr/sbin/directoryserver -u 5.2 startconsole

If running the command from the /usr/sbin/directoryserver directory works, then you hang is a result of a version compatibility issue. After you have installed the 5.2 version of Directory Server , run the following command to set the default version to 5.2.

/usr/sbin/directoryserver -d 5.2

Now you can use the various directoryserver commands with the 5.2 version of Directory Server.

You may need to confirm that the /etc/ds file contains the following settings as well:

5.1|//usr/iplanet/ds5/sbin/directoryserver|YES|YES
5.2|//usr/ds/v5.2/sbin/directoryserver|YES|NO