https://bugs.openldap.org/show_bug.cgi?id=10136
--- Comment #4 from Ondřej Kuzník <[email protected]> --- On Fri, Feb 09, 2024 at 05:09:22AM +0000, [email protected] wrote: > Ondřej Kuzník, > Thank you for checking the issue. I want to reopen this ticket as we have > identified the code which is causing the issue for us. This fix > https://bugs.openldap.org/show_bug.cgi?id=9282 is causing problem for us. > > The replication is not happening with log message like - > > 6560dc3c.54467 00000000000006B0 syncrepl_entry: rid=002 > cn=GetCollection,cn=Method Set ISVPackage,cn=Cordys > ESBServer,cn=cordys,cn=defaultInst,o=otxlab.net > 6560dc3c.54476 00000000000006B0 syncrepl_entry: rid=002 entry > 'cn=GetCollection,cn=Method Set ISVPackage,cn=Cordys > ESBServer,cn=cordys,cn=defaultInst,o=otxlab.net' > csn=20231124172411.004202Z#000000#001#000000 not new enough, ignored > > All the entries which are having the message "not new enough, ignored" is not > replicating to second LDAP. > > In our scenario, both LDAP servers are running, and we are adding entries to > server1. server2 is not stopped/restarted in between. This is reproducible > without our application, and by importing a ldif file using jxplorer. > > I have reverted this fix locally > https://git.openldap.org/openldap/openldap/-/commit/8d428f3163e56f90cb84cddfd2d5640eefc8c996, > build openldap and tested, then our scenario is working. 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? Regards, -- You are receiving this mail because: You are on the CC list for the issue.
