Well, I think I found a workaround, instead of deleting the changelog I tried
to change the max records in it, then after sending 2 or 3 update from a "good"
server the errors disappears and all updates work well.
Is it possible that there is some information in the DS configuration that doesn't
clear after changelog recreation but flush correctly after entries expire?
Now all 4 nodes works, but I hope there will be a bug-fix soon.
Thank you very much.
Dael.
Rich Megginson wrote:
Dael Maselli wrote:
> Dear Richard,
>
> The problem came back, this time in one node.
I've created a bug to track this issue -
https://bugzilla.redhat.com/show_bug.cgi?id=388021
A less drastic solution than recreating everything from scratch will be
to export the database from a good master, and reimport it into that
master, then reinit all other masters from that master. You will
probably want to make sure there are no pending updates in any of your
masters first, or you will lose them.
I'm working on a better fix for this, but in the meantime, you should
not have to reinstall everything.
--
___________________________________________________________________
Dael Maselli --- INFN-LNF Computing Service -- +39.06.9403.2214
___________________________________________________________________
Democracy is two wolves and a lamb voting on what to have for lunch
___________________________________________________________________