7.2. Common Installation Problems

First, try using the host name. If that does not work, use the fully qualified name (such as www.domain.com), and make sure the server is listed in the DNS. If that does not work, use the IP address.

If your NIS domain is different from your DNS domain, the fully-qualified host and domain name presented by the installer may be incorrect. These values must be corrected to use the DNS domain name.

You probably did not shut down a server before you upgraded it. Shut down the old server, then manually start the upgraded one.

Another installed server might be using the port. Make sure the port you have chosen is not already being used by another server.

If you are installing Directory Server in a network that uses NIS naming rather than DNS naming, you may get the following error, with incorrect.DNS.address replaced by the DNS address you attempted to use:

ERROR: Ldap authentication failed for url 
ldap://incorrect.DNS.address 

user id admin (151:Unknown error.)

Fatal Slapd Did not add Directory Server information to 
Configuration Server.

ERROR. 
Failure installing Red Hat Directory Server. 
Do you want to 
continue [y/n]? 

This error occurs when a machine is not correctly configured to use DNS naming. The default fully qualified host and domain name presented during installation is not correct. If you accept the defaults, you receive the LDAP authentication error.

To install successfully, you need to provide a fully qualified domain name that consists of a local host name along with its domain name. A host name is the logical name assigned to a computer. For example, mycomputer is a host name and example.com is a fully qualified domain name (FQDN).

A fully qualified domain name should be sufficient to determine a unique Internet address for any host on the Internet. The same naming scheme is also used for some hosts that are not on the Internet but share the same namespace for electronic mail addressing.

libjvm.so (from JRE 1.4), which the Administration Server uses to run servlets, requires that the compat-libstdc++-6.2 package be installed when running the server on Red Hat Enterprise Linux.

The package may or may not be installed depending on the options that were chosen when the operating system was installed. If the package is not installed, you get an error similar to the one in Example 7-2.

[18/Jun/2002:10:56:39] failure ( 4322): Configuration 
initialization failed:

Error running init function load-modules: dlopen of 
/export/dstest/bin/https/lib/libNSServletPlugin.so failed

(libstdc++-libc6.1-1.so.2: cannot open shared object file: 
No such file or directory)

For more information on the Sun supplied package, check the JRE's release notes at http://java.sun.com/j2se/1.4/install-linux.html.

If you forget the manager DN, you can find out what the Directory Manager DN is by looking for the nsslapd-rootdn attribute in the file serverRoot/slapd-serverID/config/dse.ldif.

If you have forgotten the Directory Manager DN password, you can reset it by doing the following:

1. Find the nsslapd-rootpw attribute in slapd.conf. If the attribute value is not encrypted in any way (that is, it does not start with {SHA} or {CRYPT}), then the password is exactly what is shown on the parameter.

2. If the attribute is encrypted, then delete the attribute value, and replace it with some cleartext value. For example, if you change the nsslapd-rootpw attribute so that it is:

   nsslapd-rootpw: my_password

   then your Directory Manager DN password is now my_password.

3. Restart your Directory Server.

4. Once your server has restarted, login as the Directory Manager and change the password. Make sure you select an encryption scheme when you do so.

For information on changing a Directory Manager password, refer to the Red Hat Directory Server Administration Guide.

Some problems may develop when you uninstall Directory Server and then reinstall. Logging has been enhanced to report setup and uninstall problems with detailed error messages to provide you with enough information to fix the problem. The setup log file is located in the following path: serverRoot/setup/setup.log. The uninstall log file, uninst.log, is stored in the system TEMP directory. This directory is usually /tmp or /var/tmp.