First of all, I hope I am not rehashing a topic that has been endlessly discussed.  I know that syncrepl gets discussed a lot from my searches, but I have not found a specific topic on my issue.

I started out with OpenLDAP 2.3, with a single provider and two consumers doing syncrepl using a refreshAndPersist type of replication.  Periodically, I would see that one or more of the consumers would fail to synchronize a change made to the provider.  A restart of the consumer would fix this and we could move on.  It was annoying, but not critical at this point.

Since then, I have become more dependent on OpenLDAP and syncrepl.  I have upgraded to 2.4 to try to fix the replication issue, but it seems worse than ever.  I now have one provider and six consumers.  The consumers randomly fail to synchronize (as evidences by contextCSN monitoring).  This happens several times a day.  I'm thinking that maybe there is something wrong with my configuratiuon.  This is what I am using:

overlay syncprov
syncprov-checkpoint 1 10
syncprov-sessionlog 100
syncprov-nopresent TRUE
syncprov-reloadhint TRUE
limits dn.exact="cn=replica,o=users,dc=domain,dc=com" time.soft=unlimited time.hard=unlimited size.soft=unlimited size.hard=unlimited

Consumers (all consumers have the exact same config):
syncrepl   rid=123
                retry="10 +"
updateref       ldap://ldap.sea.corp.domain.com

A few "weird" things:
* After the upgrade, I notice that the Directory Type on the Root DSE is still OpenLDAP 2.3
* I notice that where previously I could simple create a new consumer by installing a fresh copy of openldap, copying the config from another consumer over, and starting up to get a full copy of the directoy, it now fails to completely replicate and I have to do a full slapcat/slapadd to do the initial population.

Like I said, I hope it's just something stupid I am doing...