That's a good question! We're not sure what was the root cause of the
When we realized the replication wasn't happening, we had recently
updated FreeIPA from 3.0.0-36 to 3.0.0-37 (on CentOS 6.5) and we had
shutdown m1 and m2 in order to do a snapshot of the VMs. We've been
doing that for several months and never had a problem. Note that m3
wasn't shutdown and the replication stopped for it as well.
The configuration wasn't change so I don't think it was a
configuration problem. I did have to get a new ldap service keytab for
the m2 replica (/etc/dirsrv/ds.keytab) but not for m3.
I'll do more research on what happened and report back if I find
On Fri, Sep 5, 2014 at 4:22 PM, Martin Kosek <mko...@redhat.com> wrote:
> Good to hear Guillermo, I am glad you are back up and running. I am just
> curious, what as the root cause of your replication errors in the end? I did
> not catch that from the thread. Is it something we can fix in FreeIPA or is
> it just a configuration error?
> On 09/05/2014 08:06 PM, Guillermo Fuentes wrote:
>> m2 and m3 are now in sync!
>> After making sure ldapsearch was working both ways (m1<=>m2 and
>> m1<=>m3) using the server's keytabs (/etc/dirsrv/ds.keytab) for
>> getting the ticket, I re-initialize both replicas and they were able
>> to get updated:
>> @m2 # ipa-replica-manage re-initialize --from m1.example.com
>> @m3 # ipa-replica-manage re-initialize --from m1.example.com
>> Thanks so much for your hint Martin!
Manage your subscription for the Freeipa-users mailing list:
Go To http://freeipa.org for more info on the project