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

Re: AW: syncrepl connection / reconnect



Thorsten Mueller <Thorsten.Mueller@aachen.utimaco.de> writes:

> Here you are, the config of the second machine is identical, apart from the
> different provider

[...]
> syncprov-checkpoint 100 10
>
> syncprov-sessionlog 100
>
> # syncrepl directiv
>
> syncrepl      rid=001
>
>               provider=ldap://192.168.120.237:388
>
>               bindmethod=simple
>
>               binddn="cn=Replicator,dc=DatabaseReplication,dc=head"
>
>               credentials="fdet2zS3"
>
>               searchbase="dc=head"
>
>               starttls=critical
>
>               tls_cacert=/etc/TLS/ca-certs/trusted_CAs.pem
>
>               tls_cert=etc/TLS/client/client.pem
>
>               tls_key=etc/TLS/client/client_key.pem
>
>               schemachecking=on
>
>               type=refreshAndPersist
>
>               retry="5 12 60 +"
>
> mirrormode on

[...]

order matters, syncrepl has to be declared within a database
specification, modules are loaded last, after all database specific
configuration parameters.

-Dieter

-- 
Dieter Klünter | Systemberatung
http://dkluenter.de
GPG Key ID:8EF7B6C6
53°37'09,95"N
10°08'02,42"E