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----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
