Troubleshooting the Open Lightweight Directory Access Protocol and the Berkeley Data Base
m (1 revision)
Revision as of 17:12, 28 April 2011
To troubleshoot Open Lightweight Directory Access Protocol (OpenLDAP) and Berkeley Data Base (BDB), see the following sections:
OpenLDAP Server Not Responding
Problem: The OpenLDAP server is not responding.
Possible Cause: This problem could occur if, after a system crash, power outage, or manual shutdown, the OpenLDAP sever did not shut down gracefully, which caused data corruption.
Solution: To resolve this problem, stop the OpenLDAP server, and then recover the data. Follow these steps:
1. To stop the OpenLDAP server, enter the following command:
2. To recover the data, enter the following command:
$CISCO_CE_INSTALL_ROOT/bdb/bin/db_recover -h $CISCO_CE_INSTALL_ROOT/openldap/var/openldap-data
BDB Using Excessive Disk Space
Problem: The BDB is using excessive disk space.
Possible Cause: BDB creates transaction logs in the $CISCO_CE_INSTALL_ROOT/openldap/var/openldap-data file. If transaction logs are not purged, the BDB uses excessive disk space. For information about disk space, see the “System Requirements” and “Understanding Disk Space Calculation” sections in the Cisco Configuration Engine Installation and Configuration Guide, 3.5.
Solution: To resolve this problem, follow these steps:
1. To verify whether dbpurge.sh is running as a cron job, enter the following command:
2. If crontab –l is not in the list, run the Setup program to add it.
3. To manually purge BDB transaction logs, enter the following command: