[Date Prev][Date Next]
Re: Is fedora core 3 a ticking timebomb?
This is not an error for OpenLDAP 2.1-2.2. db_verify does not work
because we used a custom sort function in the database. The custom sort
functions were removed in OpenLDAP 2.3 to avoid this warning, but the
message is meaningless in 2.1-2.2.
I know I should just compile the Berkeley DB from source and apply the 4
patches but before I do I just want to make sure that that will end my
I'm running fedora core 3, openldap-2.2.24 from source with db4-4.2.52-6
from rpm. I can't seem to find out what if any patches are applied to
that db4 rpm and I'm seeing the same problems with my back-dbd that
others are commenting on.
After a power outage today the db was corrupt and db_verify and
db_recover did not work ( I don't have the output for that ). I flushed
the data queue and slapadd' the data back in, ran slapindex and before I
started the server wanted to see what a db_verify would look like.
db_verify: Page 1: out-of-order key at entry 37
db_verify: Page 1: out-of-order key at entry 74
db_verify: DB->verify: id2entry.bdb: DB_VERIFY_BAD: Database
I guess this needs to go into the FAQ since it has come up a number of
times on the list in the past couple days.
Better still - "this message means you need to upgrade to OpenLDAP 2.3..."
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/