----- Original Message -----
From: "Jon Detert" <jdetert(a)infinityhealthcare.com>
To: "General discussion list for the 389 Directory server project."
<389-users(a)lists.fedoraproject.org>
Sent: Thursday, March 7, 2013 10:37:54 AM
Subject: [389-users] Single Master replication : after master o.s. + dirsrv upgrade,
replication fails with
nsds5replicaLastInitStatus=3
I have a single master replicating to 2 slaves.
The master is Fedora Directory Server v1.0.4
The slaves are 389-DirectoryServer v1.2.10.
This has been working fine.
I tried to replace the single master with the same ds software as the
slaves (389-DirectoryServer v1.2.10), but I could not get
replication to work.
I'm hoping someone can help me see what I did wrong.
Problem solved, thanks to a reply Rich made to another email I sent today (thread:
[389-users] nsDS5ReplicaCredentials confusion).
The problem was:
1) I trusted that the 'reversible encryption' value of the nsDS5ReplicaCredentials
attribute, that was generated by fedora-ds v1.0.4, would work the same under 389-ds
v1.2.10. It does not.
2) I did not know the actual (i.e. clear-text) value of the password for the dn used in
the supplier's replication agreement to bind to the consumer. All I had was the
non-reversible hash.
3) Even if I reset the password of the bind-dn (on the consumer), I didn't know how to
generate the hash that I see in the nsDS5ReplicaCredentials attribute when I query the
replication agreement on the supplier.
Rich answered all these problem points in my other post today (thread: [389-users]
nsDS5ReplicaCredentials confusion).
Thanks,
Jon