Chapter 8 Troubleshooting DSCC and 5.x Console Problems

This chapter contains information to help you troubleshoot problems with the Directory Service Control Center (DSCC) and the 5.x Console, It contains the following sections:

This chapter contains the following sections:

• Possible Causes of DSCC Problems

• Collecting DSCC Troubleshooting Data

• Collecting and Analyzing 5.x Console Data

Possible Causes of DSCC Problems

The DSCC may fail for one of the following reasons:

• Sun Java Web Console is not running

• DSCC application not registered in the Sun Java Web Console

• DSCC registry has not been created

• The Application Server used for the DSCC WAR deployment is not running.

Collecting DSCC Troubleshooting Data

This section describes how to collect information about DSCC failures.

To Collect DSCC Troubleshooting Data

1. Verify that the Sun Java Web Console is running.

   # smcwebserver status Sun Java(TM) Web Console is running

2. Verify the status of the DSCC.

   /opt/SUNWdsee/dscc6/bin/dsccsetup status

   If it is running correctly, this command should give the following output:

   *** DSCC Application is registered in Sun Java (TM) Web Console *** DSCC Agent is registered in Cacao *** DSCC Registry has been created Path of DSCC registry is /var/opt/sun/dscc6/dcc/ads Port of DSCC registry is 3998 ***

3. If the status says that the DSCC application is not registered, you need to reinitialize the DSCC.

   When the DSCC application is not registered, the DSCC does not appear in the Sun Java Web Console. Reinitialize the DSCC using the following command:

   # dsccsetup console-reg

4. If the status says that the DSCC agent is not registered, reinitialize the agent.

   When the DSCC agent is not registered, the local Directory Server and Directory Proxy Server instances can not be managed from a remote DSCC. Reinitialize the agent using the following command:

   # dsccsetup cacao-reg

5. If the status message states that the DSCC registry has not been created, initialize the DSCC registry.

   When the registry does not exist, the DSCC application needs to be initialized. Initialize the registry using the following command:

   # dsccsetup ads-create

6. If the other actions do not help, run a clean setup for the DSCC.

   Running a clean setup resets the DSCC but in the process you lose the DSCC registry.

   Run each of the following commands:

   # /opt/SUNWdsee/dscc6/bin/dsccsetup dismantle #/opt/SUNWdsee/dscc6/bin/dsccsetup initialize

   These commands cleanup and reconfigure the DSCC and its agents.

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