[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Upgrade to 2.3.40 -> failed index
Quanah Gibson-Mount wrote:
--On Sunday, February 03, 2008 8:14 AM -0800 "Paul B. Henson"
<henson@acm.org> wrote:
What happened? It can't be local corruption, all three servers failed
exactly the same way. I didn't upgrade bdb, it's the exact same version
that's been running. I didn't think I needed to rebuild the db on an
upgrade from 2.3.35 to 2.3.40, was I mistaken? Should I have done a
dump/reload? Was this failure possibly a bug in 2.3.40? A bug in 2.3.35
exposed by the upgrade?
Did you stop slapd and run db_recover before upgrading to 2.3.40?
Was 2.3.35 using back-bdb, and you changed to back-hdb with 2.3.40?
No change of that sort would cause these error messages.
-----
Feb 3 03:50:36 fosse slapd[5129]: bdb(dc=csupomona,dc=edu): file dn2id.bdb
has LSN 8388745/33900185
, past end of log at 137/33937441
Feb 3 03:50:36 fosse slapd[5129]: bdb(dc=csupomona,dc=edu): Commonly
caused by moving a database fr
om one transactional database
Feb 3 03:50:36 fosse slapd[5129]: bdb(dc=csupomona,dc=edu): environment to
another without clearing
the database LSNs, or removing
Feb 3 03:50:36 fosse slapd[5129]: bdb(dc=csupomona,dc=edu): all of the log
files from a database en
vironment
This basically says that somebody zeroed out/removed the transaction log files.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/