RE: Possible issue with Openldap and bdb with bdb transaction log s

[Quanah Gibson-Mount <quanah@stanford.edu>]

--On Friday, November 12, 2004 4:07 PM -0600 "Fortin, John {PBG}" 
<John.Fortin@pepsi.com> wrote:

> Quanah,
>   Thanks for the response.  That was my first option, but unfortunately we
> cannot bulk load with slapadd because of business requirements and data
> validation; instead, he entries are being created programatically.  Also
> this fails by filling up the log directory after adding 'only' about 5000
> entries, which I would hope slapd can handle.  These entries ate up about
> 3.4 Gig of logs. I have additional space available for logfiles, but that
> doesn't seem like a great solution.
>
>   We are using bdb 4.2.52 with the 2 (at build time) available patches.
> DB_CONFIG is used to setup the logging directories and the cache size for
> the database.  I hadn't heard of DB_LOG_AUTOREMOVE.  I will look into it.
>
> These are the current entries in out DB_CONFIG:
>
> set_cachesize   		0      52428800        0
> set_lg_regionmax        1048576
> set_lg_max              10485760
> set_lg_bsize            1097152
> set_lg_dir              /var/ldapdb/slave2/logs
> set_tmp_dir             /tmp

John,

After confirming with Howard, you need the transaction patches to BDB & 
OpenLDAP found off of my website, and then to recompile both.  They fix 
exactly the problem you are having.

<http://www.stanford.edu/services/directory/openldap/configuration/bdb-build.html>
<http://www.stanford.edu/services/directory/openldap/configuration/openldap-build.html>

You may find the patches to fix a memory leak & a leak in the cache of 
interest as well.

All assume the use of OpenLDAP 2.2.18, so you'll need to upgrade to that as 
well. ;)

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html