<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 05/21/2015 02:20 PM, thierry bordaz
wrote:<br>
</div>
<blockquote cite="mid:555DCD90.4070306@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 05/21/2015 01:36 PM, Janelle
wrote:<br>
</div>
<blockquote cite="mid:555DC320.30203@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
And just like that - for no reason, they all reappeared:<br>
<br>
unable to decode {replica 16} 55356472000300100000
55356472000300100000<br>
unable to decode {replica 23} 5545d61f000200170000
5552f718000300170000<br>
unable to decode {replica 24} 554d53d3000000180000
554d54a4000200180000<br>
<br>
:-(<br>
~J<br>
<br>
</blockquote>
Hello Janelle,<br>
<br>
Those 3 RIDs were already present in Node dc2-ipa1, correct ? They
reappeared on others nodes as well ?<br>
May be ds2-ipa1 established a replication session with its peers
and send those RIDs.<br>
Could you track in all the access logs, when the op
csn=5552f718000300170000 was applied.<br>
<br>
Note that the two hexa values of replica 23 changed
(5545d61f000200170000 5552f718000300170000 vs 5553e3a3000000170000
55543240000300170000). Have you recreated a replica 23 ?.<br>
<br>
Do you have replication logging enabled ?<br>
<br>
thanks<br>
thierry<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
Hi Thierry, Mark,<br>
<br>
I have an idea how this can happen, and now I have an environment
where these show up.<br>
<br>
The changelog contains max and purge ruv, and in my changelog I
have: <br>
<br>
<br>
dbid: 0000006f000000000000<br>
entry count: 304<br>
<br>
dbid: 000000de000000000000<br>
purge ruv:<br>
{replicageneration} 51dc3bac000000640000<br>
{replica 100} 5555a759000000640000
5555a759000000640000<br>
{replica 200} 5555b3c2000000c80000
5555b3c2000000c80000<br>
{replica 300} 5555b3c20005012c0000
5555b3c20005012c0000<br>
<br>
dbid: 0000014d000000000000<br>
max ruv:<br>
{replicageneration} 51dc3bac000000640000<br>
{replica 100} 5555a759000000640000
5555d773000000640000<br>
{replica 200} 5555b3c2000000c80000
5555b3c2000000c80000<br>
{replica 300} 5555b3c20005012c0000
5555b3c20005012c0000<br>
<br>
<br>
after restarting I got: <br>
ldapsearch -LLL -o ldif-wrap=no -h localhost -p 30522 -x -D
"cn=directory manager" -w xxxxxx -b "cn=config"
"objectclass=nsds5replica" nsds50ruv<br>
dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config<br>
nsds50ruv: {replicageneration} 51dc3bac000000640000<br>
nsds50ruv: {replica 100 <a class="moz-txt-link-freetext" href="ldap://localhost:30522">ldap://localhost:30522</a>} 5555a759000000640000
5555d773000000640000<br>
nsds50ruv: {replica 200 <a class="moz-txt-link-freetext" href="ldap://localhost:4945">ldap://localhost:4945</a>} 5555b3c2000000c80000
5555b3c2000000c80000<br>
nsds50ruv: {replica 300} 5555b3c20005012c0000 5555b3c20005012c0000<br>
<br>
replica 300 is corrupted. <br>
<br>
In this env I had played by cleaning ruv for rid 300, without
disabling repl agreements from 300 (which I shoudl have done) and by
adding changes later on replica 300 (which I shouldn't). Everything
looked fine,<br>
just after stopping to dump the changelog and restarting I was in
the bad state<br>
<br>
Need to try to repeat and verify<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>