Guillaume Rousse a écrit :
Hello.
I'm trying to follow change propagations errors using delta-synrepl in search & persist mode, by using an accesslog overlay both on master and on slaves.
About the error themselves, I clearly see changes commited in the master (version 2.3.27) not being propagated to one of the slave (version 2.3.27 also), whereas propagated to the second slave (version 2.3.34), by examining the access log on both slaves.
In case it matters, the master configuration is
# log database database bdb suffix "cn=log" rootdn "cn=root,cn=log" directory /var/lib/ldap/log index entryCSN,objectClass,reqEnd,reqResult,reqStart eq
overlay syncprov syncprov-nopresent TRUE syncprov-reloadhint TRUE
# needed for replication overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 100
# access logs overlay accesslog logdb cn=log logops writes logsuccess TRUE # scan the accesslog DB every day, and purge entries older than 7 days logpurge 07+00:00 01+00:00
And the slaves configuration is: syncrepl rid=123 provider=ldaps://ldap.futurs.inria.fr type=refreshAndPersist logbase="cn=log" logfilter="(&(objectClass=auditWriteObject)(reqResult=0))" syncdata=accesslog searchbase="dc=futurs,dc=inria,dc=fr" scope=sub schemachecking=off bindmethod=simple binddn="cn=syncuser,dc=futurs,dc=inria,dc=fr" credentials=xxxxxxxxxx