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

LDAP/BDB log purging

Running openldap 2.3.32 with bdb 4.2 (and using syncrepl if that's

I need to deal with the issue of how to safely delete old bdb log files on
our many replicas.

In a previous thread, Aaron Richton wrote:
> I'd recommend DB_LOG_AUTOREMOVE. Barring that, you can run db_archive 
> manually. Check Sleepycat docs for details on either.

Well, I just ran db_archive and caused widespread chaos because most (all?)
of the replicas stopped responding to queries. (I have yet to perform a

I know that there's a bug in bdb 4.2 that causes logs to be held open even
though they're no longer required. Upgrading bdb is not on the cards right
now so I need to work around that problem by stopping and starting openldap.

So the question I have just at the moment is, when I run db_archive, should
openldap be running or not running?

I've seen nothing in any docs that suggest it should be stopped, and the bdb
docs simply imply that applications are expected to be running (but I'm not
a programmer so my I interpreted it wrongly). So I ran db_archive just after
starting openldap. Was that the wrong thing to do, and is it an obvious
cause for the meltdown?

Lesley W

Lesley Walker
Linux Systems Administrator
Opus International Consultants Ltd
Email lesley.walker@opus.co.nz
Tel +64 4 471 7002, Fax +64 4 473 3017
Level 9  Majestic Centre, 100 Willis Street, PO Box 12 343
Wellington, New Zealand