>>> Daniel Spannbauer <d...@marco.de> schrieb am 13.10.2016 um 09:22 in
Nachricht
<57ff3626.1020...@marco.de>:
> Hello,
> 
> at the moment we have an server running openSuSE 11.4 (lets call in
> server2), running openldap 2.4.23.
> Configured is a replication to/from out mainoffice (running openldap
> 2.4.17, server1).
> Replication works fine.
> 
> I wan't to replace server2 with a newer one, running openldap 2.4.33 atm.
> ----------------------------------------------
> Configuration  for replication on server2:
> 
> 
> moduleload      syncprov.la
> serverID 1 "ldap://server1.mainoffice.xxx.de";
> serverID 2 "ldap://server2.branch.xxx.de";

Try to include ":389" in the ServerID; at least we have it here and it works
(even though openldap2-2.4.26-0.65.2 (SLES11 SP4)).

> 
> overlay syncprov
> syncrepl rid=001
>         provider=ldap://server1.mainoffice.xxx.de:389
>         binddn="cn=Administrator,dc=xxx,dc=de"
>         bindmethod=simple
>         credentials=somepassowrd
>         searchbase=" dc=marco,dc=de"
>         type=refreshAndPersist
>         interval=00:00:00:10
>         retry="5 5 300 +"
>         timeout=1
> 
> mirrormode TRUE
> overlay syncprov
> syncprov-nopresent TRUE
> syncprov-reloadhint TRUE
> syncprov-checkpoint 1000 60
> ----------------------------------------------
> 
> This config works fine with the "old" 2.4.23, but on 2.4.33 I get the
> following error when I start it on the commandline with
> /usr/lib/openldap/slapd -h ldap:///   -f /etc/openldap/slapd.conf -u
> ldap -g ldap  -o slp=off -d 1
> 
> 57ff35cc read_config: no serverID / URL match found. Check slapd -h
> arguments.
> 
> Any hints about this?
> 
> regards
> 
> Daniel
> 
> 
> 
> -- 
> Daniel Spannbauer                         Systemadministration
> marco Systemanalyse und Entwicklung GmbH  Tel   +49 8333 9233-27 Fax -11
> Rechbergstr. 4-6, D 87727 Babenhausen     Mobil +49 171 4033220
> http://www.marco.de/                      Email d...@marco.de 
> Geschäftsführer Martin Reuter             HRB 171775 Amtsgericht München




Reply via email to