[389-users] Replication error

Nathan Kinder nkinder at redhat.com
Tue Jan 21 08:27:54 UTC 2014


On 01/21/2014 05:16 AM, Diego Woitasen wrote:
> On Mon, Jan 20, 2014 at 9:17 PM, Diego Woitasen <diego at woitasen.com.ar> wrote:
>> Hi,
>>  I have a replication error with 389DS. If I try a full resync,
>> replication works. But if I modify something after that, it fails. The
>> only lines that I see in the logs are:
>>
>> [20/Jan/2014:21:12:50 -0300] - _csngen_adjust_local_time: gen state
>> before 52ddb8ec0001:1390262479:0:29
>> [20/Jan/2014:21:12:50 -0300] - _csngen_adjust_local_time: gen state
>> after 52ddbb9f0000:1390263170:0:29
>> [20/Jan/2014:21:12:50 -0300] NSMMReplicationPlugin -
>> ruv_add_csn_inprogress: successfully inserted csn 52ddbb9f000000630000
>> into pending list
>> [20/Jan/2014:21:12:50 -0300] NSMMReplicationPlugin - Purged state
>> information from entry
>> uid=zzj,ou=People,ou=branch,ou=branches,dc=site,dc=ar up to CSN
>> 52d47e6b000000630000
>> [20/Jan/2014:21:12:50 -0300] NSMMReplicationPlugin - ruv_update_ruv:
>> successfully committed csn 52ddbb9f000000630000
>> [20/Jan/2014:21:12:50 -0300] NSMMReplicationPlugin - agmt="cn=main to
>> cmald" (ldap:389): State: stop_fatal_error -> stop_fatal_error
>>
>> Not very helpful for me. The last line shows an error, but it's not
>> very descriptive. What can I do to debug this? Or do you have a hint?
>>
>> Regards,
>>   Diego
>>
> 
> I've found the problem. Someone (may be me, not sure :) ) disabled the
> changelog!

Please file a ticket in our trac instance.  It would be nice to have the
error say that the changelog is disabled to give you a clue about what
is wrong.

-NGK
> 
> 
> 
> 




More information about the 389-users mailing list