Hi Sven, On Tue, Apr 05, 2005 at 01:53:26PM +0200, Sven Hartge wrote: > >Known problem. Please try upgrading to 2.2.23. 2.1.30 will not ship > >with sarge because of these and other problems. Running db4.2_recover > >in the database directory may temporarily fix those problems but they > >are going to strike again. > > I am deeply sorry, but I have to report 2.2.23 hitting the same problem > for me. > > How can this be? I thought all those bugs were elimated in 2.2 using db4.2?
I thought so as well. Did you use a DB_CONFIG file suited for your
setup? Upstream keeps talking about the problems not being caused by
corruption but by thrashing. Probably in that case the maintainer
scripts /MUST/ install a basic DB_CONFIG which will work for most cases.
I am thinking along 8MB of caches or something.
I would be very grateful if you could try that on your setup. See
/usr/share/doc/slapd/examples/DB_CONFIG for a template.
Thanks
Torsten
signature.asc
Description: Digital signature
