<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 05/07/2015 05:39 AM, Janelle wrote: </div> <blockquote cite="mid:554ADE5A.90801@gmail.com" type="cite">On 5/6/15 8:12 PM, Vaclav Adamec wrote: <blockquote type="cite">Hi, Mike Reynolds recommend cleanallruv script (IPA RUV unable to decode thread), if you are sure that's not any live replica server behind this id than just try "cleanallruv.pl -w XXXXX -b "dc=...." -r 9" Vasek On Thu, May 7, 2015 at 2:25 AM, Janelle <a class="moz-txt-link-rfc2396E" href="mailto:janellenicole80@gmail.com"><janellenicole80@gmail.com></a> wrote: <blockquote type="cite">Hi again.. Seems to be an ongoing theme (replication). How does one remove these? unable to decode: {replica 9} 553ef80e000100090000 55402c39000000090000 I am hoping this is a stupid question with a really simple answer that I am simply missing? ~J -- Manage your subscription for the Freeipa-users mailing list: <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/freeipa-users">https://www.redhat.com/mailman/listinfo/freeipa-users</a> Go to <a class="moz-txt-link-freetext" href="http://freeipa.org">http://freeipa.org</a> for more info on the project </blockquote> </blockquote> Thank you Vasek, I am curious however. I have been running OpenLDAP configs with 20 or more servers in replication for over 5 years. In all that time, I think I have had replication issues 5 times. In the 6 months of working with FreeIPA, replication issues are constant. From reading the threads, I am not the only one in this predicament. Is there any history on why replication is so problematic in FreeIPA? regards ~J </blockquote> Hi Janelle, <blockquote>This is a large question and I have no precise answer. My understanding of OpenLDAP replication vs RHDS replication is that it is not based on the same approach syncrepl vs replica_agreement. Both are working. Replication is complex and when I compare RHDS with others DS implementation using the same approach (replica_agreement) I can say that RHDS is doing a good job in terms of performance, stability and robustness. Replication is sensitive to administrative tasks, backup-restore, reinit, upgrade, schema update. This is possibly your case we have seen 'unable to decode' during upgrade/cleanruv and still investigating that bug. thanks thierry </blockquote> </body> </html>