On 08/04/2015 06:14 PM, Janelle wrote:
you probably did run into this issue:
On 8/4/15 9:06 AM, Ludwig Krispenz wrote:
No. That is why I am baffled. I want to re-add the server to help with
loading, but obviously if it still shows up - so weird. Looks like
ldapmodify is going to be required. I don't even have any strange
CSN/replicas that can't be decoded in list-ruv
On 08/04/2015 05:40 PM, Rob Crittenden wrote:
don't know if I want to know the answer, but is it contained in the
Just to keep your Tuesday fun, is this possible:
ipa-replica-manage list <---- shows all 16
1 of the servers broke a couple of weeks ago and was removed with
"clean-ruv" but STILL shows up in the replica list, but not a single
master has a replica agreement with it, so there is no way to
since trying to do "ipa-replica-manage del" with any options,
force, from ANY servers says there is no replica agreement. How is
possible and how do I get rid of the phantom replica? and I did try
--cleanup and it took it, but did nothing. And there is NOTHING in the
To further clarify, it is not a CA either, and never was.
Very confusing indeed. I just like to keep the developers on their
ioa-replica-manage del failed to delete the master because it did not
remove all services before. If you want to do it by ldapmodify, check
what services are there below the master entry and remove these befor
removing the master
list shows the those entries in cn=masters,cn=ipa,cn=etc,$SUFFIX. It
doesn't show agreements or topology.
What output do you see when --cleanup is used?
You should check the 389-ds access log after this is run as well to
see what searches and mods were attempted.
Manage your subscription for the Freeipa-users mailing list:
Go to http://freeipa.org for more info on the project