Troubleshooting the Open Lightweight Directory Access Protocol and the Berkeley Data Base

From DocWiki

Revision as of 11:03, 19 May 2011 by Hsivakum (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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:

  /etc/init.d/NetAppOpenLDAP stop

2. To recover the data, enter the following command:

  $CISCO_CE_INSTALL_ROOT/bdb/bin/db_recover -h 

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 is running as a cron job, enter the following command:

  crontab –l

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:


OpenLDAP Server throws error during setup of Configuration Engine on Solaris

Problem: During Setup of Solaris server the appliance-setup.log reports "javax.naming.NamingException: [LDAP: error code" as mentioned below

  javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
  at com.sun.jndi.ldap.LdapCtx.mapErrorCode(
  at com.sun.jndi.ldap.LdapCtx.processReturnCode(
  at com.sun.jndi.ldap.LdapCtx.processReturnCode(
  at com.sun.jndi.ldap.LdapCtx.connect(
  at com.sun.jndi.ldap.LdapCtx.<init>(
  at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(
  at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(
  at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(
  at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(
  at javax.naming.spi.NamingManager.getInitialContext(
  at javax.naming.InitialContext.getDefaultInitCtx(
  at javax.naming.InitialContext.init(
  at javax.naming.InitialContext.<init>(
  javax.naming.NamingException: [LDAP: error code 80 - internal error]; remaining name 'ou=config,ou=CNSApplications,ou=configengine,o=ica,c=se'
  at com.sun.jndi.ldap.LdapCtx.mapErrorCode(
  at com.sun.jndi.ldap.LdapCtx.processReturnCode(
  at com.sun.jndi.ldap.LdapCtx.processReturnCode(
  at com.sun.jndi.ldap.LdapCtx.c_bind(
  at com.sun.jndi.ldap.LdapCtx.c_bind(
  at com.sun.jndi.toolkit.ctx.ComponentContext.p_bind(
  at com.sun.jndi.toolkit.ctx.PartialCompositeContext.bind(
  at com.sun.jndi.toolkit.ctx.PartialCompositeContext.bind(
  at javax.naming.InitialContext.bind(

Possible Cause: The Solaris Server on which Cisco Configuration Engine is being is containing zones(containers).

Solution: Cisco Configuration Engine is certified on a Solaris Server with Zone. Please install Cisco Configuration Engine only on non zoned Solaris Server's.

Rating: 5.0/5 (1 vote cast)

Personal tools