[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4551) refreshOnly fails if provider is ever unreachable

On Tue, 2006-05-16 at 22:36 +0000, Darren.Gamble@sjrb.ca wrote:

> But, when we simulated network problems, we were able to break replication
> fairly easily.
> If the consumer is ever unavailable (slapd is not running, or if the host is not
> reachable), then the consumer will log the failure ("do_syncrep1:
> ldap_sasl_bind_s failed (-1)") but never, ever try again.  Replication will be
> broken until someone manually restarts the consumer's slapd (assuming the
> provider is available at that time, of course).  If this is done, then the
> consumer will resync again right away, and seems to work until the next problem
> occurs.
> Here's the syncrepl config section (low interval for testing purposes):
> syncrepl rid=123
>         provider=ldap://A.B.C.D:389
>         type=refreshOnly
>         interval=00:00:05:00
>         searchbase="o=Shaw Cablesystems,c=CA"
>         scope=sub
>         schemachecking=on
>         updatedn="cn=consumeradmin,o=Shaw Cablesystems,c=CA"
>         bindmethod=simple
>         binddn="cn=readuser,o=Shaw Cablesystems,c=CA"
>         credentials=xxxxxxx

You seem to have missed the "retry" parameter to syncrepl, which allows
to define the retry strategy in case of failure.  I suggest you continue
discussing this type of problems on the openldap-software mailing list,
as there appears to be no evidence of a software bug so far.


Ing. Pierangelo Masarati
Responsabile Open Solution
OpenLDAP Core Team

SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
Office:   +39.02.23998309          
Mobile:   +39.333.4963172
Email:    pierangelo.masarati@sys-net.it