Le 01/04/2016 01:26, Jussi Sallinen a écrit :
Hi,
How you managed to get this working or did you come up with a workaround: http://www.openldap.org/lists/openldap-technical/201201/msg00205.html
I have a similar situation where I'm doing a reprovision of my 2nd multimaster replica virtualhost and adding base config etc. with ldapadd (we build it from scratch with Ansible during reprovisioning). After the new multimaster replica comes up it has newer timestamps than the current up & running replica from where this new one is supposed to replicate everything as we use ldapadd during the reprovision phase with Ansible.
hello,
after you create the seed replica, you just have to "touch" the master to ensure the timestamp on the master is newer than on the replica.
As the seed configuration only contains 3 objects: cn=config, olcDatabase={-1}frontend,cn=config and olcDatabase={0}config,cn=config, I do it that way:
$ ldapmodify -H ldap://master ...credentials... <<EOF dn: cn=config changetype: modify
dn: olcDatabase={-1}frontend,cn=config changetype: modify
dn: olcDatabase={0}config,cn=config changetype: modify EOF
best regards, Jephté Clain
openldap-technical@openldap.org