https://bugs.openldap.org/show_bug.cgi?id=10136
--- Comment #5 from Ondřej Kuzník ondra@mistotebe.net --- On Fri, Feb 09, 2024 at 11:57:48AM +0000, openldap-its@openldap.org wrote:
That code very much has to remain, if the consumer was told it is up to date to CSN x, then any further messages tagged with x or older *have to* be ignored. The issue is likely to be elsewhere. Can you provide logs of the previous replication sessions up to the offending CSN?
Also still waiting for the provider side of things: - configuration - logs
Without that it will be hard to tell what happened.
BTW, I think you might have done that already but if deltasync is in effect, make sure ACLs give the replica user full access to both accesslog and the replicated DB.
Thanks,