[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
DB_CONFIG - Auto remove logs
- To: openldap-technical@openldap.org
- Subject: DB_CONFIG - Auto remove logs
- From: ldap@mm.st
- Date: Tue, 08 Feb 2011 14:48:02 -0700
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=message-id:from:to:mime-version:content-transfer-encoding:content-type:subject:date; s=smtpout; bh=jN5FtjrHveoDky8Sa19kgmaf6bY=; b=CMBVWwUs+EpUJ27EFasEgfDqbbj1bUmZG58XFk9dGc653kB06lUhcFRDibGN70E8cSC5rRNHa8MUnz06d6DAcCB4XxEu2JT6Nl4uS9yXAPmQrEmkWMQ7Xg0uQWgVGRUP3PfRa8ksomMNI2nKz3eOt3ToveKK6bce5Q6k6zGXSfo=
This may have been discussed, but i can not seem to find out why the
transaction logs are not getting removed when I use DB_LOG_AUTOREMOVE in
DB_CONFIG. This is on a Redhat 5 openldap 2.3 server.
DB_CONFIG has the following:
set_lg_dir /var/lib/ldap/bdblogs
set_flags DB_LOG_AUTOREMOVE
Doing slapd_db_archive shows about 134 unused files.
I then did the following (is this the correct procedure to use when
updating DB_CONFIG?):
> serivice ldap stop
> Edited DB_CONFIG
> slapd_db_recover
> slapd_db_archive
> service ldap start
The files are still there. I also manually did a checkpoint with
"slapd_db_checkpoint -1" and verified the transaction log time changed.
Reran "slapd_db_archive" and it outputs the same files. I read that
earlier versions required a patch for this to work, but I was not sure
about this one. I'm unclear on when the removal is suppose to take
place, but it doesn't seem to be working.