I don't see any fix done for syncrepl on 2.4.36. Speaking about the actual problem i have noticed that the do_syncrep* is not getting triggered as defined in the config:  

interval=00:00:05:00
retry="60 +"

and get triggered after long delay about ~23hrs or so. Not sure if this a bug.

Thanks,
Ashok


On Sun, Nov 10, 2013 at 6:14 AM, Quanah Gibson-Mount <quanah@zimbra.com> wrote:
I suggest you read the openldap changelog and upgrade to 2.4.36. 

--Quanah

On Nov 9, 2013, at 12:34 AM, Ashok Kumar Shah <ashok.shah@flipkart.com> wrote:

I have upgraded to OpenLDAP 2.4.31. I was hoping that the syncrepl issue will subside with the upgrade, but problem continue to persist even now. Just to point out that the master still runs the older version i.e 2.4.31, but i guess that should be ok since the issue is with the replication or perhaps with contextCSN not getting updated on the client(slaves).

Thanks,
Ashok 


On Mon, Jul 15, 2013 at 3:47 AM, Quanah Gibson-Mount <quanah@zimbra.com> wrote:
--On Sunday, July 14, 2013 10:35 PM +0530 Ashok Kumar Shah <ashok.shah@flipkart.com> wrote:


I am running OpenLDAP 2.4.23.

I would advise you to run a modern release.  I would strongly advise you to read the changes log since 2.4.23.


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