Cisco Cisco Agent Desktop 8.5 Guida Alla Risoluzione Dei Problemi
LDAP Monitor Problems
March 2012
83
■
Check if slapd.exe is running. If it is not running, follow the
troubleshooting steps for this problem.
troubleshooting steps for this problem.
■
The LDAP database is corrupted. Follow the steps outlined in
Problem
Clients do not find the same information from LDAP after failing over
from one LDAP to the other.
from one LDAP to the other.
Solution
Some solutions:
■
Ensure replication is set up correctly in the CAD Configuration
Setup utility. For more information, see the Cisco CAD Installation
Guide.
Setup utility. For more information, see the Cisco CAD Installation
Guide.
■
Check that registry entries for LDAP Host 1 and 2 on both CAD
services computers are the same and contain the right information.
services computers are the same and contain the right information.
■
Check that slapd.conf on both CAD services computers are correct
and reference each other.
and reference each other.
■
If all else fails, follow the steps outlined in
.
Problem
The database directory contains many log files that are consuming a
large amount of disk space. The rate of accumulation depends on the
number of updates made to LDAP. For example, 10,000 updates
consume approximately 25 MB. Log file names have the format
log.0000001.
large amount of disk space. The rate of accumulation depends on the
number of updates made to LDAP. For example, 10,000 updates
consume approximately 25 MB. Log file names have the format
log.0000001.
Solution
Restarting LDAP Monitor service on a regular basis will remove log files.
Problem
After shutting down Directory Services replication, the LDAP Host
registry entries on the clients are not automatically updated.
registry entries on the clients are not automatically updated.
Solution
Update the LDAP Host 1 registry entry on each client to reflect the
correct server location. Clear the other LDAP Host registry entries.
correct server location. Clear the other LDAP Host registry entries.