On 06/23/2015 01:44 PM, Marc Wiatrowski wrote:
So I have 3 servers, spider01a, spider01b, and spider01o
[root@spider01a]$ ipa-replica-manage list-ruv
Directory Manager password:
spider01a.iglass.net:389 <http://spider01a.iglass.net:389>: 12
spider01o.iglass.net:389 <http://spider01o.iglass.net:389>: 13
spider01b.iglass.net:389 <http://spider01b.iglass.net:389>: 7
spider01a.iglass.net:389 <http://spider01a.iglass.net:389>: 5
[root@spider01b]$ ipa-replica-manage list-ruv
Directory Manager password:
spider01b.iglass.net:389 <http://spider01b.iglass.net:389>: 7
spider01a.iglass.net:389 <http://spider01a.iglass.net:389>: 12
spider01a.iglass.net:389 <http://spider01a.iglass.net:389>: 5
spider01o.iglass.net:389 <http://spider01o.iglass.net:389>: 13
[root@spider01o]$ ipa-replica-manage list-ruv
Directory Manager password:
spider01o.iglass.net:389 <http://spider01o.iglass.net:389>: 13
spider01a.iglass.net:389 <http://spider01a.iglass.net:389>: 12
spider01b.iglass.net:389 <http://spider01b.iglass.net:389>: 7
spider01a.iglass.net:389 <http://spider01a.iglass.net:389>: 5
I'm not seeing any issues, but there is only one spider01a (which was
replaced at some point) Is the duplicate spider01a a problem? This a
case for using clean-ruv?
Yes it is.
You need to know which replica id (5 or 12) is the old/invalid rid. You
can look at /etc/dirsrv/slapd-INSTANCE/dse.ldif on spider01a, and look
for nsDS5ReplicaId. The value you find is your current rid, so you can
clean the other one. However it is possible that both 5 and 12 are
valid. Each backend can have its own replication config - so once again
look for all the nsDS5ReplicaId attributes to verify if its being used
or not.
Mark
If so, is there a way tell which one to run it on?
thanks,
Marc
--
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go to http://freeipa.org for more info on the project
