[Date Prev][Date Next]
Re: kill -INT corrupts database (ITS#1982)
Content-Type: text/plain; charset=us-ascii; format=flowed
--On Sunday, August 25, 2002 10:13 PM +0000 Howard Chu=20
> Your report didn't indicate which backend you are using. I am unable to
> reproduce this error on our Solaris 8 system, using either back-bdb or
> back-ldbm. I am unaware of any patches relevant to this behavior either.
> Do you have debugging enabled on the slave slapd before it's terminated?
> Are there any error messages associated with the shutdown?
We were using Berkeley DB v3 on our system. Also, we noted the order in=20
which we killed things seemed to stop the problem from ocurring. However,=20
the systems just all got upgraded to Berkeley DB v4 and OpenLDAP-2.1.4, and =
we changed our replication method to use SASL/GSSAPI, so I'm not sure we'll =
be able to reproduce it either.
Senior Systems Administrator
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----