Your message dated Sat, 16 Apr 2005 03:00:09 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [fixed in 2.2.23] database corruption
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 20 Jan 2005 16:16:53 +0000
>From [EMAIL PROTECTED] Thu Jan 20 08:16:53 2005
Return-path: <[EMAIL PROTECTED]>
Received: from openbsd.xs4all.nl (router.cacholong.nl) [80.126.240.96]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrezN-0004Lh-00; Thu, 20 Jan 2005 08:16:53 -0800
Received: from localhost (localhost [127.0.0.1])
by router.cacholong.nl (Postfix) with ESMTP id 46B942952
for <[EMAIL PROTECTED]>; Thu, 20 Jan 2005 17:16:57 +0100 (CET)
Received: from router.cacholong.nl ([127.0.0.1])
by localhost (jgc.homeip.net [127.0.0.1]) (amavisd-new, port 10024)
with LMTP id 16508-04; Thu, 20 Jan 2005 17:16:55 +0100 (CET)
Received: from monster.cacholong.nl (unknown [192.168.20.6])
by router.cacholong.nl (Postfix) with ESMTP id 34FD47AD;
Thu, 20 Jan 2005 17:16:55 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Matthijs Mohlmann <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: slapd: Index and Data corruption with openldap2 2.1.30
X-Mailer: reportbug 3.5
Date: Thu, 20 Jan 2005 17:16:48 +0100
Message-Id: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at jgc.homeip.net
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: slapd
Version: 2.1.30-3
Severity: critical
Justification: causes serious data loss
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
We are running debian sarge on some of our servers now and are getting
data and index corruption (every few weeks). On different servers
(configured the same) we experience those problems. I think it is
openldap that causes this problem because openldap 2.2 doesn't have this
problems with the same bdb backend. (db4.2)
We only use this option in DB_CONFIG but i think it doesn't have
anything to do with the problem:
set_cachesize 0 52428800 0
I've searched the logs for any inconsistency but i couldn't find anything
in the logs.
Another little problem i experienced is the bad performance with 2.1.30
i've benched 2.1.30 and 2.2.20 a little bit and i got this:
On the server (openldap 2.1.30):
IBM eServer series: 1 Ghz with 1.5 Gb RAM (Kernel: 2.6.8)
www0:~# time id user_from_ldap
uid=1003(user_from_ldap) gid=1003(user_from_ldap) groups=1003(user_from_ldap)
real 0m1.588s
user 0m0.059s
sys 0m0.017s
the real is between the 1.4 to 1.8 seconds.
Desktop system (openldap 2.2.20)
Pentium 2 350Mhz with 192Mb RAM (Kernel: 2.6.8)
desktop:~# time id user_from_ldap
real 0m0.388s
user 0m0.059s
sys 0m0.017s
The real on this one is between 0.2 and 0.4 seconds.
On both machines ldap is running on localhost.
I've now a few weeks openldap 2.2 running on my desktop system and i
didn't get any data or index corruption and it's fast as hell.
I've seen that the main blocker is the gnutls patch. Well i ported the
patch almost to 2.2.20. There are a few things i have to look for. And
then i hope it will work. I don't know how far you are with that patch
but i hope, really hope that 2.2.20 can make it into Sarge.
If you need more information please mail me.
Regards,
Matthijs Mohlmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFB79lw2n1ROIkXqbARAnC9AJ9t2O8g+r4l6NAxLYXAnSKgTTy8OQCgsdPd
e4hE3GCHUOI+QWxD6aU8FGc=
=FRFn
-----END PGP SIGNATURE-----
---------------------------------------
Received: (at 291408-done) by bugs.debian.org; 16 Apr 2005 10:00:09 +0000
>From [EMAIL PROTECTED] Sat Apr 16 03:00:09 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain)
[66.93.39.86]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DMk5x-0004Kj-00; Sat, 16 Apr 2005 03:00:09 -0700
Received: by localhost.localdomain (Postfix, from userid 1000)
id 42F3E171D59; Sat, 16 Apr 2005 03:00:09 -0700 (PDT)
Date: Sat, 16 Apr 2005 03:00:09 -0700
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [fixed in 2.2.23] database corruption
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="ILuaRSyQpoVaJ1HG"
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
--ILuaRSyQpoVaJ1HG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
As slapd 2.2.23 has now slipped into testing (which was eventually our
intention anyway), this particular bug is presumably fixed; there are other
new ones that need to be dealt with, but none that any longer match this
description.
Cheers,
--=20
Steve Langasek
postmodern programmer
--ILuaRSyQpoVaJ1HG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCYOIoKN6ufymYLloRAs4lAJwKUM+w1q9cYEfsLdYacbDip3n6KwCgrSdi
QqC8oS8OdI+C8qe8Wplc7no=
=9Q9A
-----END PGP SIGNATURE-----
--ILuaRSyQpoVaJ1HG--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
