Thank you very much! That does it.
On 7 April 2016 at 13:12, Ludwig Krispenz wrote:
>
> On 04/07/2016 07:23 AM, Prashant Bapat wrote:
>
> What I have done now was to add a new server, ipa02 and configured
> replication again and things are fine.
>
> However on IPA1 the 389 ds error logs have ref
On 04/07/2016 07:23 AM, Prashant Bapat wrote:
What I have done now was to add a new server, ipa02 and configured
replication again and things are fine.
However on IPA1 the 389 ds error logs have reference to the dead ipa2
replica.
[07/Apr/2016:04:13:11 +] NSMMReplicationPlugin -
agmt="
What I have done now was to add a new server, ipa02 and configured
replication again and things are fine.
However on IPA1 the 389 ds error logs have reference to the dead ipa2
replica.
[07/Apr/2016:04:13:11 +] NSMMReplicationPlugin - agmt="cn=
meToipa2.example.net" (ipa2:389): Replication bin
# ipa-replica-manage list `hostname`
ipa2.example.net: replica
ipa3.example.net: replica
ipa4.example.net: replica
ipa2.example.net should not be there. How do I remove it?
On 6 April 2016 at 18:55, Rob Crittenden wrote:
> Prashant Bapat wrote:
>
>> Hi,
>>
>> We had 4 IPA servers in master mast
Prashant Bapat wrote:
Hi,
We had 4 IPA servers in master master mode with all of them connected to
each other.
IPA1 <> IPA2 (colo 1)
IPA3 <> IPA4 (colo 2)
One of the replica servers (IPA2) had to be rebuild.
So I went ahead and used below commands.
ipa-replica-manage disconnect IPA
Oh this is FreeIPA version 4.1.4 on FC21.
On 6 April 2016 at 16:03, Prashant Bapat wrote:
> Hi,
>
> We had 4 IPA servers in master master mode with all of them connected to
> each other.
>
> IPA1 <> IPA2 (colo 1)
>
> IPA3 <> IPA4 (colo 2)
>
> One of the replica servers (IPA2) had to be