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

RE: Openldap 2.1.29/bdb/corrupted database

To: Quanah Gibson-Mount <quanah@stanford.edu>
Subject: RE: Openldap 2.1.29/bdb/corrupted database
From: Rodrigo Gesswein <rodri@chilesat.net>
Date: Wed, 19 May 2004 09:19:41 -0400 (CLT)
Cc: openldap-software@OpenLDAP.org
In-reply-to: <FE819416F0C28ABA2D323208@cadabra-dsl.stanford.edu>
References: <B6DE0C3D9243E64782272C508B3089908B8CF6@svexmb01.merc-int.com> <Pine.LNX.4.56.0405061126130.6170@pluton.chilepac.com> <Pine.LNX.4.58.0405061141210.28550@ebova.hiz.rqh> <Pine.LNX.4.56.0405061306450.6170@pluton.chilepac.com> <E0EC0218D4D914BE65C637FB@cadabra-dsl.stanford.edu> <Pine.LNX.4.56.0405061349190.6170@pluton.chilepac.com> <FE819416F0C28ABA2D323208@cadabra-dsl.stanford.edu>

Hi!

   Sorry for late answer, but finally I migrated mi ldap backend from
BDB 4.1.25 to 4.2.52, and now every work fine...


> BDB 4.1.25 is particularly problematic if you have a cache that is too
> small.  You should really use BDB 4.2.52 + patches.


   I understand, can anybody recommend a DB_CONFIG file for my ldap 2.1.30
under Debian and with aprox. 15.000 entries. Any fine tunning tips will be
very apreciated too.

   Thank you!

Rodrigo!

Follow-Ups:
- RE: Openldap 2.1.29/bdb/corrupted database
  - From: Quanah Gibson-Mount <quanah@stanford.edu>

References:
- RE:
  - From: Tim Walker <twalker@merc-int.com>
- RE:
  - From: Rodrigo Gesswein <rodri@chilesat.net>
- RE: Openldap 2.1.29/bdb/corrupted database
  - From: Frank Swasey <Frank.Swasey@uvm.edu>
- RE: Openldap 2.1.29/bdb/corrupted database
  - From: Rodrigo Gesswein <rodri@chilesat.net>
- RE: Openldap 2.1.29/bdb/corrupted database
  - From: Quanah Gibson-Mount <quanah@stanford.edu>

Prev by Date: Re: Access Control by Organizational Unit?
Next by Date: Add entries...
Index(es):
- Chronological
- Thread