You can turn on loglevel sync to see related messages. As to "force a sync"...well, you can provide an explicit cookie on the command line?
On Thu, 6 Sep 2007, Emmanuel Dreyfus wrote:
Hello
I have some objects that are not propagated by syncrepl. How this should be debugged? Is there a way to force a sync?
Even if I stop slapd, rm /var/openldap/openldap-data/* and restart it, syncrepl will repopulate the databases, but I'll stil have some objects missing.
It's 2.3.38, and here is syncrepl config stuf: provider=ldap://ldap0.example.net type=refreshAndPersist searchbase="dc=example,dc=net" starttls=critical bindmethod=sasl saslmech=EXTERNAL schemachecking=off retry=3,1,10,2,60,+
One odd thing: The root entryCSN is newer on the replica than on the master. Can it explains the mess?
-- Emmanuel Dreyfus manu@netbsd.org