[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: openldap up; can't db_stat
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quanah Gibson-Mount wrote:
|
|
| --On Wednesday, July 21, 2004 10:15 AM -0500 Digant Kasundra
| <digant@uta.edu> wrote:
|
|>
|> Hello everyone,
|>
|> My slapd is up and responsive (and accurate). But running db_stat gives
|> me the following error:
|>
|> db_stat: fatal region error detected; run recovery
|> db_stat: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
|>
|> And running db_recover (with slapd stoppped) gives me the following
|> error:
|>
|> db_recover: unable to join the environment
|> db_recover: Ignoring log file: log.0000000001: unsupported log version 8
|> 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: fatal region error detected; run recovery
|> db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
|> recovery
|
|
| Are the db_stat, db_recover commands you are running from the same
| version of BDB OpenLDAP is using? A discussion I read from googling on
| your error indicated you can see something like this if you happen to
| use a BDB 4.1 db_recover/db_stat and a BDB 4.2 database... RH often
| throws a lot of crap on their boxes, so it may be that a 4.1 set of
| binaries is coming up in your path before a 4.2 set of binaries.
In the RH/Fedora case (and Mandrake since 10.0), you should not be
running db_stat on any openldap data files, but slapd_db_stat. Same
goes for db_recover and slapd_db_recover.
Regards,
Buchan
- --
Buchan Milne Senior Support Technician
Obsidian Systems http://www.obsidian.co.za
B.Eng RHCE (803004789010797)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA/q4WrJK6UGDSBKcRAgaPAJ9VCtk9HGwMUGOUfwbBmq+WTS48rwCeO/I6
grBoroQWq7NpbUeXvLGI/44=
=niKB
-----END PGP SIGNATURE-----