Red Hat Directory Server B.08.00 for HP-UX Release Notes and Supplemental Instructions

Troubleshooting
This section describes problems you might encounter and how to resolve them. For more
information, see the Red Hat Directory Server 8.0 Installation Guide.
Server Cannot Allocate Import Cache for Replica Initialization
The Directory Server allocates one import cache for each online replica initialization operation.
If you configure a large import cache size it is possible to configure an import cache size that is
so large that the server cannot allocate the cache for replica initialization. This is most likely to
occur if multiple replica initialization operations are initiated on the same server simultaneously.
To avoid this problem, use the default value for the import cache size or configure an import
cache size that is significantly smaller than the available physical memory.
Replication Error Using Admin Express
To monitor replication status using Admin Express, be sure that the Administration Server has
read permissions to the replication monitoring configuration file. If not, the Administration
Server returns an error message.
Setup Script Displays Could not connect to ldap Error
If you run the setup-ds-admin.pl setup script and attempt to register a new Directory Server
with a Configuration Directory Server, the Configuration Directory Server and the user data
server must be valid and running. If they are not, the script displays an error similar to the
following:
Could not connect to ldap://host:389 for bind DN admin status=151
Verify the LDAP URL for the Configuration Directory Server and re-enter it as necessary. If the
registration still fails, the remote server might be down and the installation cannot proceed. For
more information, see the sections "Determine the Location of the Configuration Directory" and
"Determine the Location of the User Directory" in the Red Hat Directory Server Installation Guide.
The Server Is Not Responding
If a Directory Server does not seem to be responding, you can use the following ldapsearch
command to verify that the server is still functioning.
/opt/dirsrv/bin/ldapsearch -h hostname -p port_number -s base -b ""
"objectclass=*"
where:
hostname
Is the LDAP server name or IP address
port_number
is the LDAP server TCP port number.
For a functioning server, the following command displays information from the Directory Server,
including the name of the suffix (namingContexts):
./ldapsearch -h ldapserver.example.com -p 389 -s base -b ""
"objectclass=*"
The output is similar to the following:
dc:
objectClass: top
namingContexts: o=netscaperoot
namingContexts: dc=example,dc=com
supportedExtension: 2.16.840.1.113730.3.5.7
supportedExtension: 2.16.840.1.113730.3.5.8
supportedExtension: 2.16.840.1.113730.3.5.3
supportedExtension: 2.16.840.1.113730.3.5.5
supportedExtension: 2.16.840.1.113730.3.5.6
supportedExtension: 2.16.840.1.113730.3.5.9
Troubleshooting 33