[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: How stop ldap in this version.

--On Wednesday, March 22, 2006 7:30 PM +0000 ricardo.ferreira@cimsoft.pt wrote:


# Software Specifications
 - OpenLDAP v2.3.20
 - SleepyCat   v4.4

When i stop ldap by kill the process i canÂt acess my database.

# I try slapd -d -1 and gave me this

backend_startup_one: starting "dc=Cimsoft,dc=pt"
bdb_db_open: dc=Cimsoft,dc=pt
bdb_db_open: unclean shutdown detected; attempting recovery.
bdb_db_open: dbenv_open(/usr/local/var/openldap-data)
slapd starting
daemon: added 4r
daemon: added 7r
daemon: added 8r
daemon: select: listen=7 active_threads=0 tvp=zero
daemon: select: listen=8 active_threads=0 tvp=zero

# I try db_recover -c -h /usr/local/var/openldap-data/   and gave me this

db_recover: Program version 4.3 doesn't match environment version
db_recover: Unacceptable log file
/usr/local/var/openldap-data/log.0000000001: unsupported log version 11
db_recover: Invalid log file: log.0000000001: Invalid argument
db_recover: PANIC: Invalid argument
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database

My database will be corrupted when i kill the process? How stop ldap in this version?

Don't kill your slapd process with kill -9

use kill -INT or something else that isn't fatal

Also, you obviously have multiple version of BDB present (4.3 and 4.4). You need to use the db_recover command that OpenLDAP is linked against (you used a 4.3 db_recover instead of a 4.4 db_recover).

I will note that OpenLDAP 2.3.20 does *automatic* recover though, so you shouldn't be running db_recover at all.


-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html