Thanks Quanah , Yuri ,
 
I belive I should do both synch clocks closely  and use opeldap version 2.4.26 instead 2.4.23?
Due to time difference in clocks my replication was not working(CSN too old),when I manually added dummy entry, the replication started working (as CSN entry updated).
So for any reason if clocks goes out of sync, is there any other solution/work around to this issue ?
 
Thanks
Rupesh
 
On Sun, Sep 4, 2011 at 2:59 AM, Yuri Bank <yuribank@gmail.com> wrote:
Hmm. I thought you only needed NTP time sync with N-way and MMR. But not with single Provider. I guess I never noticed an issue with this since my servers run ntp ayways.

On Sat, Sep 3, 2011 at 1:57 PM, Quanah Gibson-Mount <quanah@zimbra.com> wrote:
--On Saturday, September 03, 2011 1:02 AM -0700 Yuri Bank <yuribank@gmail.com> wrote:

I'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 "CSN too old,
ignoring" error messages spam endlessly in your consumer logs?

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).

Wrong.  Your clocks should *always* be tightly in sync.  Particularly with the advent of delta-sync MMR in the next release.

--Quanah


--

Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra ::  the leader in open source messaging and collaboration