Re: bdb 4.6 issue with 2.4.12

[Quanah Gibson-Mount <quanah@zimbra.com>]

--On Friday, October 17, 2008 8:28 PM +0200 Guillaume Rousse 
<Guillaume.Rousse@inria.fr> wrote:

> Quanah Gibson-Mount a Ãcrit :
> > --On Friday, October 17, 2008 4:22 PM +0200 Guillaume Rousse
> > <Guillaume.Rousse@inria.fr> wrote:
> >
> > > Since I upgraded one of my server from 2.4.11 to 2.4.12, I'm facing
> > > heavy database issues:
> > > [root@etoile ~]# slapcat -b dc=msr-inria,dc=inria,dc=fr
> > > ...
> > > bdb(dc=msr-inria,dc=inria,dc=fr): pthread lock failed: Invalid argument
> > > bdb(dc=msr-inria,dc=inria,dc=fr): PANIC: Invalid argument
> > > bdb(dc=msr-inria,dc=inria,dc=fr): PANIC: DB_RUNRECOVERY: Fatal error,
> > > run database recovery
> > > bdb(dc=msr-inria,dc=inria,dc=fr): PANIC: fatal region error detected;
> > > run recovery
> > > bdb_db_close: database "dc=msr-inria,dc=inria,dc=fr": close failed:
> > > DB_RUNRECOVERY: Fatal error, run database recovery (-30975)
> > >
> > > Even importing a backup ldiff file on a fresh installation triggers the
> > > same problems.
> > >
> > > I tested this problem on two different environment (mandriva 2008.1,
> > > mandriva cooker), and one user reported it against mandriva 2009.0
> > > (https://qa.mandriva.com/show_bug.cgi?id=45034). This seems to either
> > > imply an openldap or a packaging issue. Should I report an ITS for this,
> > > or rather provide more informations ?
> >
> > What options was BDB 4.6 compiled with?  Does it have all the patches
> > from Oracle?
> According to the spec file, there is one oracle and two fedora patches
> applied:
>
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/db46/current/S
> PECS/db46.spec?revision=293611&view=markup
>
> The exact option list used is a bit more difficult to tell, given the
> usage of conditional build options, but it seems to be:
> --enable-shared --enable-static --enable-rpc
> --enable-cxx
> --disable-posixmutexes --with-mutex=x86/gcc-assembly (or
> --with-mutex=x86_64/gcc-assembly for x86_64).

I'd suggest rebuilding BDB with:

--enable-posixmutexes --with-mutex=POSIX/pthreads

and then rebuilding OpenLDAP against the new BDB build, and see if the 
problem persists.

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration