Search Engine: Elastic

Article ID: 5476, created on Jul 17, 2008, last review on May 9, 2014

  • Applies to:
  • Operations Automation


LDAP server can be started, however it does not listen to port 389 and does not actually work, the 'slapcat' utility being run on LDAP server hangs too.

The error like this may be observed trying to restart LDAP service:

# service ldap restart
Stopping slapd:                                        [  OK  ]
Checking configuration files for slapd:  bdb_db_open: unclean shutdown detected; attempting recovery.
bdb_db_open: Recovery skipped in read-only mode. Run manual recovery if errors are encountered.
config file testing succeeded                          [  OK  ]
Starting slapd:                                        [  OK  ]

Another symptom of the problem is that POA tasks fail with the error message 'Syncing Internal IP Resolver Database with external data source', the example is below:

Synchronization failed. LDAP IP ''. Internal IP Resolver's service returned error: Can't contact LDAP server. IP '', host '', operation delete.


LDAP back-end database is corrupted.


Use the slapd_db_recover utility on the LDAP server to recover the database, for example:

# /etc/init.d/ldap stop
# mkdir /root/ldap_backup
# cp -a /var/lib/ldap/* /root/ldap_backup/
# slapd_db_recover -v -h /var/lib/ldap
db_recover: Finding last valid log LSN: file: 1 offset 263805
db_recover: Recovery starting from [1][261683]
db_recover: Recovery complete at Thu Jul 17 08:29:23 2008
db_recover: Maximum transaction ID 80000175 Recovery checkpoint [1][264861]
# /etc/init.d/ldap start

WARNING: Always backup database files before working with the database, for standard installation LDAP database files are located in the /var/lib/ldap folder.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF