[Pkg-openldap-devel] Bug#494219: Bug#494219: openldap: FTBFS: test failed - master and R2 slave databases differ

Steve Langasek vorlon at debian.org
Fri Aug 8 02:34:20 UTC 2008


severity 494219 important
tags 494219 moreinfo unreproducible
thanks

On Thu, Aug 07, 2008 at 07:54:55PM -0300, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> i386.

> > >>>>> Starting test019-syncreplication-cascade ...
> > running defines.sh
> > Starting master slapd on TCP/IP port 9011...
> > Using ldapsearch to check that master slapd (pid=10359) is running...
> > Using ldapadd to create the context prefix entry in the master...
> > Starting R1 slave slapd on TCP/IP port 9012...
> > Using ldapsearch to check that R1 slave slapd (pid=10594) is running...
> > Starting R2 slave slapd on TCP/IP port 9013...
> > Using ldapsearch to check that R2 slave slapd (pid=12247) is running...
> > Starting P1 slave slapd on TCP/IP port 9014...
> > Using ldapsearch to check that P1 slave slapd (pid=13990) is running...
> > Starting P2 slave slapd on TCP/IP port 9015...
> > Using ldapsearch to check that P2 slave slapd (pid=16231) is running...
> > Starting P3 slave slapd on TCP/IP port 9016...
> > Using ldapsearch to check that P3 slave slapd (pid=18369) is running...
> > Using ldapadd to populate the master directory...
> > Waiting 25 seconds for syncrepl to receive changes...
> > Using ldapmodify to modify master directory...
> > Waiting 25 seconds for syncrepl to receive changes...
> > Using ldapsearch to read all the entries from the master...
> > Using ldapsearch to read all the entries from the R1 slave...
> > Using ldapsearch to read all the entries from the R2 slave...
> > Using ldapsearch to read all the entries from the P1 slave...
> > Using ldapsearch to read all the entries from the P2 slave...
> > Using ldapsearch to read all the entries from the P3 slave...
> > Filtering master ldapsearch results...
> > Filtering R1 slave ldapsearch results...
> > Filtering R2 slave ldapsearch results...
> > Filtering P1 slave ldapsearch results...
> > Filtering P2 slave ldapsearch results...
> > Filtering P3 slave ldapsearch results...
> > Comparing retrieved entries from master and R1 slave...
> > Comparing retrieved entries from master and R2 slave...
> > test failed - master and R2 slave databases differ
> > >>>>> /build/user-openldap_2.4.10-3-amd64-asswdk/openldap-2.4.10-3/tests/scripts/test019-syncreplication-cascade failed (exit 1)
> > make[3]: *** [bdb-mod] Error 1

> The full build log is available from:
>    http://people.debian.org/~lucas/logs/2008/08/07

> A list of current common problems and possible solutions is available at 
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

> About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
> of the Grid'5000 platform, using a clean chroot containing a sid i386
> environment.  Internet was not accessible from the build systems.

This failure isn't reproducible on my system, or on any of the buildds.  Is
there some reason that 25 seconds would not be long enough of a delay for
openldap changes to propagate in your build environment?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org





More information about the Pkg-openldap-devel mailing list