[Freeipa-devel] Changelog error after re-initialize. [WAS [PATCH] 0080 ..]

[Rich Megginson]

On 02/01/2011 09:14 AM, Simo Sorce wrote:
> On Tue, 01 Feb 2011 09:07:58 -0700
> Rich Megginson<rmeggins at redhat.com>  wrote:
>
>> On 01/31/2011 09:07 PM, Rob Crittenden wrote:
>>> Simo Sorce wrote:
>>>> On Mon, 31 Jan 2011 18:38:47 -0500
>>>> Simo Sorce<ssorce at redhat.com>   wrote:
>>>>
>>>>> See also ticket #887
>>>>>
>>>>> Simo.
>>>>>
>>>> With a patch file it works better I guess :-)
>>>>
>>>> Simo.
>>>>
>>>>
>>> I wasn't entirely sure how to test this so I use ipa-replica-manage
>>> re-initialize --from=master.example.com
>>>
>>> It seemed to work, not sure how I can really tell. I did notice
>>> this in my 389-ds error log:
>>>
>>> [31/Jan/2011:23:05:59 -0500] - import userRoot: Import complete.
>>> Processed 159 entries in 4 seconds. (39.75 entries/sec)
>>> [31/Jan/2011:23:06:00 -0500] NSMMReplicationPlugin -
>>> multimaster_be_state_change: replica dc=example,dc=com is coming
>>> online; enabling replication
>>> [31/Jan/2011:23:06:00 -0500] NSMMReplicationPlugin -
>>> replica_reload_ruv: Warning: new data for replica dc=example,dc=com
>>> does not match the data in the changelog.
>>>   Recreating the changelog file. This could affect replication with
>>> replica's  consumers in which case the consumers should be
>>> reinitialized.
>> This should be ok.  This basically means "hey, your database has just
>> be reloaded".  The server should wipe out the changelog and create a
>> new one.
> Is this something the server will do automatically?
Yes.
> Or is it an action we need to add to our scripts ?
No.
> Simo.
>
>