Buchan Milne [mailto:firstname.lastname@example.org]
> 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
You ran db_archive for the first time, on *all* replicas at
the same time????
Yes. We administer 80+ servers that are more or less identically
configured, and typically perform small admin tasks in "for" loop, which
is what I did in this case.
> 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
This may or may not be the cause of your problems.
Additionally, this is
affected by your database configuration and checkpointing settings.
> So the question I have just at the moment is, when I run
> openldap be running or not running?
It should be safe, depending on your configuration, to run
However, due to the tasks it does (just deleting all the
unused log files
would have a similar effect), it can be quite IO intensive,
and you may incur
IO starvation when doing it, impacting performance of any
using files on the same block devices (e.g. slapd).
As an additional piece of background, we are currently running all the
replication out of an intermediate server (it's a transistional setup). As
far as I can tell, it all hit the fan when the db_archive ran on that
intermediate server. Obviously I should have left that one out of the list
but I didn't think of it at the time.
These are all the non-comment entries in DB_CONFIG:
set_cachesize 0 268435456 1
Database definition entries in slapd.conf: