Hi,
Pierangelo Masarati ando@sys-net.it writes:
Dieter Kluenter wrote:
Hello, Pierangelo Masarati ando@sys-net.it writes:
Dieter Kluenter wrote:
"Dieter Kluenter" dieter@dkluenter.de writes:
Mavric Domen d.mavric@iskratel.si writes:
[...]
initial contextCSN on localhost contextCSN: 20081022151212.263032Z#000000#000#000000 initial contextCSN on remote peer contextCSN: 20081022151212.263032Z#000000#000#000000 after a modification on localhost entryCSN: 20081022151026.029523Z#000000#000#000000 on remote peer contextCSN: 20081022151212.263032Z#000000#000#000000 I just wonder wether this is a new bug or is it silly me.
AFAIK, the SID in each contextCSN should be anything but "000" (it should be the serverID of the server that received the write and propagated the modification).
OK, than I presume that is a bug, unless I get other comments I will file an ITS.
What is your configuration on all servers? In detail, what's the value of the serverID statements, of the syncrepl statements and what's the URI you're running them with?
Solved it, silly me! The initial slapd.conf should only contain one serverID statement without any additional address, only after starting all peers the serverID has to be modified to include all participating peers.
-Dieter