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

Re: Transaction log files generated too frequently and DB_LOG_AUTOREMOVE setting does not remove old log files

To: Joanne Yan Fu <fuyyan@yahoo.com>, "openldap-technical@openldap.org" <openldap-technical@openldap.org>
Subject: Re: Transaction log files generated too frequently and DB_LOG_AUTOREMOVE setting does not remove old log files
From: Michael Ströder <michael@stroeder.com>
Date: Sat, 13 May 2017 12:56:28 +0200
In-reply-to: <1214004296.232703.1494553997770@mail.yahoo.com>
Openpgp: id=43C8730E84A20E560722806C07DC7AE36A8BC938
References: <1214004296.232703.1494553997770.ref@mail.yahoo.com> <1214004296.232703.1494553997770@mail.yahoo.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 SeaMonkey/2.48

Joanne Yan Fu wrote:
> I have a relatively small OpenLDAP DB
> 
> Here are some settings and server information:
> 
>   * OpenLDAP: slapd 2.4.23 on linux
> 
>   * In slapd.conf:
>     database    bdb

Next month release 2.4.23 is seven years old.
There have been many, many fixes since then.

While it is possible to tweak the BDB transaction logs settings my recommendation is you
should do yourself a favour and

1. upgrade to a recent OpenLDAP release (currently 2.4.44) and

2. migrate to back-mdb which does not have transaction log files at all

Ciao, Michael.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

References:
- Transaction log files generated too frequently and DB_LOG_AUTOREMOVE setting does not remove old log files
  - From: Joanne Yan Fu <fuyyan@yahoo.com>

Prev by Date: Re: Client binding to a specific local address
Next by Date: Re: Client binding to a specific local address
Index(es):
- Chronological
- Thread