> Ok, what brought this up is that about every week
Ahh yes, this is the default replication purge interval (7 days)
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/8....
<
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/8....
Look for nsDS5ReplicaPurgeDelay
It could also be changelog trimming:
http://www.port389.org/docs/389ds/FAQ/changelog-trimming.html
<
http://www.port389.org/docs/389ds/FAQ/changelog-trimming.html>
So what this is telling me is that one of your replication agreements was over a week
behind from the other replicas (not good). Was that agreement disabled for a while, and
then enabled, for some reason?
Not that I’m aware of. I’m using the repl-monitor script to monitor our replication and
everything is inline (no CSN mismatch) until all of a sudden that happens.
Since I’m not an expert on ldap, do you mind posting the ldapsearch command to look up the
value of nsDS5ReplicaPurgeDelay. I’m getting an empty value back. The subdirs of
/var/lib/dirsrv/INSTANCE are:
bak
cldb
db
ldif
Is cldb the changelog db?