[Date Prev][Date Next] [Chronological] [Thread] [Top]

Index corruption after multiple updates

I have a definate problem with index corruption under 2.0.23. The
problem can be solved in the short run by doing a slapcat removing the
DB files and doing a slapadd -- the problem usually reoccurs within 24
hours. (commenting out the affected index also fixes the problem but (of
course) has a big performance impact). Running slapindex does NOT fix
the problem. This problem is occuring on the master and on the slaves.
The version of _all_ software on each is identical (we run cfengine so
I'm sure of this) The version information is as follows:

	Linux 2.4.2-2 
	Red Hat Linux release 7.1 (Seawolf)

	configure information
		--enable-wrappers \
                --enable-cleartext \
                --with-cyrus-sasl \
                --enable-spasswd \
                --enable-kpasswd \
                --with-kerberos=k5 \
                --enable-ipv6=no \
                --with-tls \

Are there any known issues with db 3.1.17?? I couldn't find any open
bugs at http://www.openldap.org/its/ 
Could this be thread or concurrency related?? I haven't built a test
harness yet to be able to reproduce the problem, but that shouldn't be
too hard.



Paul Fleming
SIU School of Medicine
Springfield Il USA