Quanah Gibson-Mount wrote:

QGM> What version of BDB? Was BDB self compiled? What options QGM> were used to compile BDB in either case?

In the case from which the backtrace came, it's the system (ie Debian packaged) BDB 4.6.21. A quick glance at debian/rules suggests it at least starts with CFLAGS="-O2" and runs configure with

--prefix=/usr \ --mandir=$${prefix}/share/man \ --localstatedir=/var \ --sysconfdir=/etc \ --libexecdir=/usr/lib \ --enable-cxx \ --enable-compat185 \ --enable-rpc \ --enable-tcl \ --with-tcl=/usr/lib/tcl8.4 \ --enable-test plus --enable-java

Is that what you need to know?

QGM> I will note that there's known problems with using BDB QGM> under Xen given certain compile options

I'm aware of that from doing Cyrus deployments under Xen. Anyway, we're not using Xen in this case precisely so we don't have to worry about that.

QGM> I don't know whether or not QEMU is affected.

As far as I know it isn't, but to exclude that possibility we posted the bug based on three slapds on the same - bare metal - machine.

What makes you think it could be a "blame Berserkley" problem? Is it worth re-testing with a different backend and/or a private controlled build of BDB?

Cheers

Duncan