RE: Replication fails after network outage

["Darouichi, Aziz" <adarouic@post03.curry.edu>]

Hi Aaron,

I do have keep alive in the slapd.conf:

syncrepl rid=006
  provider=ldap://192.168.19.43
  tls_cert=/etc/pki/tls/certs/ldap-tls.curry.edu.cert.pem
  tls_key=/etc/pki/tls/private/ldap-tls.curry.edu.key.pem
  tls_cacert=/etc/pki/tls/certs/cacert.pem
  tls_reqcert=demand
  searchbase="dc=curry,dc=edu"
  schemachecking=on
  timelimit=unlimited
  sizelimit=unlimited
  type=refreshAndPersist
  retry="60 +"
  keepalive=240:10:30



-----Original Message-----
From: Aaron Richton [mailto:richton@nbcs.rutgers.edu] 
Sent: Wednesday, November 13, 2013 10:08 AM
To: Darouichi, Aziz
Cc: openldap-technical@openldap.org
Subject: Re: Replication fails after network outage

On Wed, 13 Nov 2013, Darouichi, Aziz wrote:

> Hi,
> 
> We are running 2 replicas one local and the other is remote.  When there is a network interruption replication fails and I have to delete the entire database in the remote replica, and let it re-synch again.
> 
> Is there a way to make the remote continue its replication after the network connection is established without having to delete the database or restart the services?

See slapd.conf(5) for the "keepalive" parameter to the "syncrepl" 
directive.