Michael Ströder wrote:
Chris Card wrote:
> I am running openldap 2.4.36 with BDB for my main backend db, and
replication setup using delta-syncrepl with MDB for the
> I monitor the contextCSN to check that replication is in sync, but I've
noticed what looks like a bug:
> If I try to delete a non-existent DN from the main db on machine A, I
the delete attempt in the cn=accesslog db on machine A with status 32, but
contextCSN of the main db is not changed, as expected.
> On machine B the contextCSN of the main db is updated, as if the delete
succeeded, and then machine A appears to be behind machine B according to
> Is this a known bug?
In delta-syncrepl the consumer is supposed to be configured to only receive
updates from the log whose reqResult=0. Otherwise the consumer shouldn't
receive anything at all.
Are you using slapo-memberof or slapo-refint?
If yes, you're probably hitting ITS#7710 which was fixed recently in OpenLDAP
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/