Re: openldap-2.0.23 mirror/multimaster neverending updates

["Pierangelo Masarati" <masarati@aero.polimi.it>]

Olle.Westman@astrazeneca.com writes: 

> Hi, I've managed to setup two openldap server on different machines that
> update each other depending on what server received an update request. 
> The result should be a HA-solution where it doesn't matter if one of the
> servers go down. It works. They do update each other.
> But when one server updates the other, the other server recognizes the
> update and tries to update the first server again!
> So they never stop updating each other with the same info. How can i make
> this behaviour stop?
>  I don't want openldap trying to update a source that is already updated.
> Maybe there is some timestamp info that this can be used for? 
> -Olle Westman 

I assume you compiled the server enabling multimaster operations;
then you should do something like: 

<server 1 slapd.conf>
updatedn    "cn=server 2,dc=your,dc=org"
replica     host=server2.your.org
          binddn="cn=server 1,dc=your,dc=org"
          ...
</server 1 slapd.conf> 

<server 2 slapd.conf>
updatedn    "cn=server 1,dc=your,dc=org"
replica     host=server1.your.org
          binddn="cn=server 2,dc=your,dc=org"
          ...
</server 2 slapd.conf> 

In this case changes to server 1 will result in replication to
server 2 with binddn "cn=server 1,dc=your,dc=org", which is
recognized as the updatedn, and changes coming from that dn
are not replicated back.  The same applies to changes that are
performed on server 2. 

Pierangelo. 

Dr. Pierangelo Masarati               | voice: +39 02 2399 8309
Dip. Ing. Aerospaziale                | fax:   +39 02 2399 8334
Politecnico di Milano                 | mailto:pierangelo.masarati@polimi.it
via La Masa 34, 20156 Milano, Italy   | http://www.aero.polimi.it/~masarati