[Freeipa-users] Replication Agreement issues noticed with repl-monitor.pl

Petr Vobornik pvoborni at redhat.com
Fri Jul 15 08:00:35 UTC 2016


On 07/15/2016 08:17 AM, Martin Kosek wrote:
> You should be able to succeed with "ipa-replica-manage del <removed-server>"
> and --force/--cleanup flags:

but first call ipa-csreplica-manage del <server> --force/--cleanup

> 
> $ man ipa-replica-manage
> ...
>        -c, --cleanup
>               When  deleting  a  master with the --force flag, remove leftover
>               references to an already deleted master.
> ...
> 
> Martin
> 
> On 07/14/2016 05:35 PM, Devin Acosta wrote:
>> ipa01-jap was a host that is no more, is there a simple way to clear these 
>> replication agreements to clean it up?
>>
>> On Thu, Jul 14, 2016 at 7:14 AM, Petr Vobornik <pvoborni at redhat.com 
>> <mailto:pvoborni at redhat.com>> wrote:
>>
>>     On 07/14/2016 12:57 PM, Martin Kosek wrote:
>>      > On 07/13/2016 04:24 AM, Devin Acosta wrote:
>>      >>
>>      >> I was trying to create another Replica but then noticed it was
>>     constantly having
>>      >> issues trying to finish the joining of the replication. I then ran the
>>     command:
>>      >> repl-monitor.pl <http://repl-monitor.pl> <http://repl-monitor.pl>, It
>>     appears i have several replicaid's
>>      >> and they seem to be having issues, wondering if this is adding to my issue.
>>      >>
>>      >> Anyone know how I can resolve this issue and clean up the replication???
>>      >>
>>      >> See attached Screenshot.
>>      >
>>      > I wonder if cleaning RUVs help:
>>      >
>>      >
>>     https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/trouble-replica.html#trouble-repl-cleanruv
>>      >
>>
>>     dangling RUVs
>>
>>     1. "Can't acquire busy replica"
>>     seems OK if it disappears after a while.
>>
>>     2. "1 Unable to acquire replicaLDAP error: Can't contact LDAP"
>>     Probably worth investigating if ipa01-
>>     i2x.rsinc.local:389 and ipa01-
>>     jap.rsinc.local:389 still exist. If not then there is probably a
>>     dangling replication agreement for o=ipaca suffix.
>>
>>     --
>>     Petr Vobornik
>>
>>
> 


-- 
Petr Vobornik




More information about the Freeipa-users mailing list