[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Replication sucks :-)
>>> Marc Schoechlin <ms-ldap@bart.LF.net> 01/16/04 11:16am >>>
Hi !
I tried to setup a simple replication without ssl.
Everything seems to be o.k - but it simply doesn t work :-)
I see successful replication in the replication-log - but
the entries on the salve remain in the old state:
--
replica: 10.1.1.21:389
time: 1074242734
dn: uid=test,ou=EDV,ou=People,dc=testdomain,dc=de
changetype: modify
delete: street
street: werwer
-
add: street
street: Finkenweg 123
-
replace: entryCSN
entryCSN: 2004011608:45:34Z#0x0001#0#0000
-
replace: modifiersName
modifiersName: cn=admin,dc=testdomain,dc=de
-
replace: modifyTimestamp
modifyTimestamp: 20040116084534Z
-
==> /var/lib/ldap/replog: file truncated <==
--
There are no real negative entries in the syslog of both systems.
I use Debian/Sarge with OpenLDAP/slapd : 2.1.23-1
I did the following - whats wrong ?
--
master-Server : 10.1.1.11
slave-Server : 10.1.1.21
[master : step 1]
$$ /etc/init.d/slapd stop
[Slave : step 2]
$$ /etc/init.d/slapd stop
"/etc/ldap/slapd.conf":
--
updatedn="cn=admin,dc=testdomain,dc=de"
updateref="10.1.1.11:389"
--
[master : step 3]
* copy the database
$$ slapcat > ~/out
$$ scp ~/out root@10.1.1.21:
* change the config
"/etc/ldap/slapd.conf":
global-section:
--
replogfile /var/lib/ldap/replog
--
database-definition:
--
replica uri=ldap://10.1.1.21:389
"binddn=cn=admin,dc=testdomain,dc=de"
bindmethod=simple credentials=myadminpasswd
--
[slave : step 4]
$$ cd /var/lib/
$$ tar zcvf ../ldap-backup.tgz ldap
$$ rm -f ldap/*
$$ slapadd -l /root/out -f /etc/ldap/slapd.conf
$$ /etc/init.d/slapd start
[master : step 5]
$$ /etc/init.d/slapd start
$$ tail -f /var/lib/ldap/replog
--
--
Gruss / Best regards | LF.net GmbH | fon +49 711 90074-413
Marc Schoechlin | Ruppmannstr. 27 | fax +49 711 90074-33
ms@LF.net | D-70565 Stuttgart | http://www.lf.net
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Hi Marc,
Is slurpd running on the master server? I do not see it in your list of
commands, unless /etc/init.d/slapd on the master starts slurpd also,
which in a stock installation, it does not!
AFIK, the slapd process sees from the config file that there is
replication to be done and writes the replication file. The slurpd
process is the one responsible for reading the file generated by slapd
and actually sending the info to the replicated servers.
Mike.