I&#39;ve seen a very similar issue (ContextCSNs being newer on my consumers), and I believe it was fixed in OpenLDAP (2.4.26). Do the <span style="font-size:10pt;font-family:Arial">“CSN too old, ignoring” error messages spam endlessly in your consumer logs?</span><br>
<br>As for your other questions. You only need a single accesslog, and the clocks on your consumer nodes do not need to be in synch with the Provider (in deltasync replication).<br><br>-Yuri<br><br><div class="gmail_quote">
On Thu, Sep 1, 2011 at 12:39 PM, Rupesh Thakkar <span dir="ltr">&lt;<a href="mailto:rupeshthakkar@gmail.com">rupeshthakkar@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Other than original query , I have additional queries about delta replication.<br>
If have more than one consumers, do I need to decalre seprate access<br>
logs for each of the replica ?<br>
If I want to use changelog insteadof acesslog, where can I find documentation ?<br>
<br>
Regards<br>
<font color="#888888">Rupesh<br>
</font><div><div></div><div class="h5"><br>
On 9/1/11, Rupesh Thakkar &lt;<a href="mailto:rupeshthakkar@gmail.com">rupeshthakkar@gmail.com</a>&gt; wrote:<br>
&gt; Do my both provider and slave machines needs times synched using NTP or lag<br>
&gt; of few seconds is allowed (1-2 seconds)?<br>
&gt;<br>
&gt; Thanks<br>
&gt; Rupesh<br>
&gt;<br>
<br>
</div></div></blockquote></div><br>