Hi
Does that preclude you building your own OpenLDAP server on that platform? Using vendor built slapd is not recommended for a variety of reasons.
Not really an easy option for a variety of reasons. Anyway I'd rather understand the problem first than just upgrade without knowing why I'm doing so.
But not 100% ruled out either.
Have you tried stopping slapd and running db_recover on the database? Note that you cannot run that command while slapd is running.
Yes.
# /etc/init.d/ldap stop
Shutting down ldap-server done
# pgrep slapd
# cd /var/lib/ldap/
# ls -l
total 276
drwx------ 3 ldap ldap 4096 Aug 7 20:19 .
drwxr-xr-x 27 root root 4096 Aug 7 04:15 ..
-rw------- 1 ldap ldap 16384 Aug 7 20:19 __db.001
-rw------- 1 ldap ldap 278528 Aug 7 20:19 __db.002
-rw------- 1 ldap ldap 98304 Aug 7 20:19 __db.003
-rw------- 1 ldap ldap 450560 Aug 7 20:19 __db.004
-rw------- 1 ldap ldap 24576 Aug 7 20:19 __db.005
-rw------- 1 ldap ldap 32768 Aug 7 20:15 dn2id.bdb
-rw------- 1 ldap ldap 131072 Aug 7 23:21 id2entry.bdb
-rw-r----- 1 ldap ldap 1612 Aug 7 23:21 log.0000000001
-rw------- 1 ldap ldap 16384 Aug 7 20:15 objectClass.bdb
-rw------- 1 ldap ldap 8192 Aug 7 20:20 userPassword.bdb
# db_recover
db_recover: Log sequence error: page LSN 1 520; previous LSN 1 98700
db_recover: Recovery function for LSN 1 452 failed on forward pass
db_recover: PANIC: Invalid argument
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
# db_recover -V
Sleepycat Software: Berkeley DB 4.2.52: (June 30, 2004)
#
Maybe I'm using the too wrong? I note that after I run the erring db_recover the __db.00X files are gone.
Kevin