test

Sun Java System Directory Server Enterprise Edition 6.1 Troubleshooting Guide

Chapter 2 Troubleshooting Installation and Migration Problems

This chapter provides information to help you troubleshoot problems with installation and migration. It includes the following topics:

Possible Causes of an Installation Problem

A problem installing Directory Server Enterprise Edition could be caused by one of the following:

If you encounter a problem doing an upgrade, confirm that you are installing the same type of software distribution as you installed previously. For example, if you installed before using the zip distribution, any upgrade you make must also use the zip distribution.

If you are installing a SunAlert patch, confirm in the read me that you are installing the patch number that applies to your type of distribution.

Troubleshooting Java ES Installation Problems

This section describes how to troubleshoot problems installing the Java Enterprise System software distribution on Solaris and Linux operating systems.

Note –

If the problem concerns a general installation failure for Java Enterprise System, first check the installation troubleshooting chapter in the Installation Guide for your version of Java Enterprise System.

General Recommendations

Before you begin troubleshooting your Java ES installation, be certain that you have done your installation using the Java ES installer. You must install the Java ES distribution using this installer. The installer installs a large number of component packages.

Troubleshooting Java ES Installations on Solaris

This section provides information to help you troubleshoot problems installing Directory Server Enterprise Edition on Solaris using the Java ES distribution.

Collecting and Analyzing Data

Review the installation errors logs for information about what occurred during the installation failure. On Solaris, search for error messages in the /var/sadm/install/logs directory. On Red Hat and HP-UX systems, installations logs are located in the /var/opt/sun/install/logs directory. On Windows systems, installation logs are located in the C:\Docuemnts and Settings\current-user\Local Settings\Temp directory.

The logs directory contains the following log files:

Information about the installed components, including Directory Server, are included in these log files.

Contacting Sun Support

If you cannot complete Directory Server Enterprise Edition installation using the Java ES distribution on Solaris and are unable to troubleshoot your problem, collect the following data. This data can help the Sun Support Center resolve your problem.

In addition to the data described here, see To Collect Required Debug Data For Directory Server Installation Problems in Sun Gathering Debug Data for Sun Java System Directory Server 5.

Troubleshooting Java ES Installations on Linux

If you installed the Java Enterprise System distribution manually, meaning you installed only the packages you thought were required, restart a clean installation using the installer.

Procedure To Do a Clean Reinstall of Java ES on Linux

  1. Stop all of the Java ES processes.

  2. Remove everything under the install-path that you specified during the configuration phase.

    To help you locate this path, run the following:


    # grep location /var/tmp/productregistery

  3. Remove the /var/tmp/productregistry file and the /var/opt/sun/install/productregistry file.

    These product registry files contain a description of what packages have been installed for Java ES and where they were installed.

  4. Uninstall the Directory Server Enterprise Edition RPM packages.

    Locate all of the installed Directory Server Enterprise Edition RPM packages as follows:


    # rpm -qa | grep 'sun-ldap-(shared|directory|proxy|console)'

    Remove all of the RPM packages you locate as follows:


    # rpm -e list-of-rpm-packages

  5. Install the package again using the Java ES installer

Resolving a Java ES Permissions Problem

If after performing a clean install you still cannot launch the installer, you may be experiencing a problem with permissions. This problem typically occurs on Linux because of an incorrect default umask value. This problem arises when you install as one user, such as root, then use a regular LDAP user for Directory Server. When you launch Directory Server as the LDAP user, it fails because this user does not have access to files that have been installed as root because of a umask value that is too restrictive.

For example, you can reset the permissions using a simple script as follows:


# cd /opt/sun
# for i in `find . -perm 750`
do
chmod $i 755 $i
done
# for i in `find. -perm 640`
do
chmod $i 644 $i
done
# cd instance-directory
# for i in `find . -perm 750`
do
chmod $i 755 $i
done
# for i in `find . -perm 640`
do 
chmod $i 644 $i
done

Contacting Sun Support

If you cannot complete Directory Server Enterprise Edition installation using the Java ES distribution on Linux and are unable to troubleshoot your problem, collect the following data. This data can help the Sun Support Center resolve your problem.

In addition to the data described here, see To Collect Required Debug Data For Directory Server Installation Problems in Sun Gathering Debug Data for Sun Java System Directory Server 5.

Troubleshooting Zip Installation Problems

This section provides information to help you troubleshoot problems using the zip distribution for Directory Server Enterprise Edition installation.

If you are installing Directory Server Enterprise Edition on a host machine that already contains an installation of the Java Enterprise System, then the common agent container port may already be in use. To provide an alternate port for the common agent container, use the dsee_deploy -p port command.

If you cannot complete Directory Server Enterprise Edition installation using the zip distribution, collect and analyze the following data. If the source of the error is not apparent, send this data to the Sun Support Center for help resolving your problem.

Troubleshooting Migration Problems

If you encounter problems during a Directory Server Enterprise Edition migration, collect and analyze the following data. If the source of the error is not apparent, send this data to the Sun Support Center for help resolving your problem.

Troubleshooting Problems Installing Directory Server 5.2

Review the installation errors logs for information about what occurred during the installation failure. On Solaris, search for error messages in the /var/sadm/install/logs directory. On Red Hat and HP-UX systems, installations logs are located in the /var/opt/sun/install/logs directory. On Windows systems, installation logs are located in the C:\Docuemnts and Settings\current-user\Local Settings\Temp directory.

The Directory_Server_install.Atimestamp log file records installation summary information and the Directory_Server_install.Btimestamp log file contains more detailed log messages. For example, the detailed log file for a Directory Server installation that failed on December 16 at 3:32 p.m. would have a name like Directory_Server_install.B12161532.

To use the log files for troubleshooting, attempt to isolate the first problem that occurred. Often, the first problem leads to successive problems. Review the logs as follows:

  1. Review the installation summary log file (A), which provides a high-level description of what was installed and configured. If a problem occurred, see what component caused the problem. If multiple problems occurred, isolate the first.

  2. Review the detailed log file (B). Look for the first error warning that occurred and attempt to resolve it. Sometimes resolving one error resolves a number of seemingly unrelated errors that follow.

    Find the name of the component or package that caused the problem.

The log files can give you clues that determine your next steps. For example, if there was a configuration problem, look at the configuration summary to examine the settings you used. If there was a directory conflict, check that you did not specify a directory that is reserved by a different component product.