[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: BDB-4.2.52 bug (Was Initial 2.2.4 exploration results)
- To: <openldap-software@OpenLDAP.org>
- Subject: RE: BDB-4.2.52 bug (Was Initial 2.2.4 exploration results)
- From: "David Parker" <david.parker@rocketsoftware.com>
- Date: Thu, 15 Jan 2004 11:39:34 -0500
- Content-class: urn:content-classes:message
- Thread-index: AcPbAVkNoMlbixFFRqCPiEt5ULi9qwAhJMHQ
- Thread-topic: BDB-4.2.52 bug (Was Initial 2.2.4 exploration results)
On that patch, I assume that the lines marked with a "+" should be added, and the lines marked with a "-" should be deleted?
Thanks.
- DAP
> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Quanah
> Gibson-Mount
> Sent: Wednesday, January 14, 2004 7:39 PM
> To: openldap-software@OpenLDAP.org
> Subject: BDB-4.2.52 bug (Was Initial 2.2.4 exploration results)
>
>
>
>
> --On Wednesday, January 07, 2004 4:07 PM -0800 Quanah Gibson-Mount
> <quanah@stanford.edu> wrote:
>
>
> > I've also had one case under syncRepl that changes made to
> the master
> > didn't end up in the master's DB when the replica had been
> attached, then
> > de-attached, and the BDB ended up being corrupted, causing
> me to have to
> > run db_recover before the master would work again, and
> having to re-add
> > the changes.
>
> This is due to a bug in BDB 4.2.52. All users of BDB-4.2.52
> should apply
> the following patch:
>
> <http://www.sleepycat.com/update/4.2.52/patch.4.2.52.html>
>
> (Thanks Howard for finding this!)
>
> I've verified that applying this patch removes this deadlock
> situation.
>
> --Quanah
>
> --
> Quanah Gibson-Mount
> Principal Software Developer
> ITSS/TSS/Computing Systems
> ITSS/TSS/Infrastructure Operations
> Stanford University
> GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
>
>