I've had a similar problem here. I don't really have much to add in the way of info for tracking it down, but here is an additional question:
Once a replica server gets out of sync w/ the master in this way, how does one get the replica back in sync? I've not been able to figure that out, short of deleting the entire database on the replica and rebuilding it from scratch, which can take a very long time.
On Fri, Sep 28, 2007 at 03:20:18PM +0200, Stelios Grigoriadis wrote:
I have upgraded openldap to latest stable version (2.3.38) and used Berkeley DB version 4.5.20. The problem remains. I realize my analisys wasn't correct since, as Howard Chu pointed out, the CSN contains both a timestamp and a counter. So the entryCSN:s are unique.
But, the problem remains and I have no idea why this happens. I somehow still suspect that the problem still is in the initial phase of the sync operation (refresh stage). It might be that, some of the not-yet committed modifications don't make it into the result set in the search operation. Later after another entry is added, the "lost" entries are never to be synced over.
I will test some more and try to provide more information. I have a test program that generates this problem but it is a little cumbersome. I will try to slim it down and use more common schema elements before posting it.
Regards
/Stelios