On 12/12/2014 02:00 PM, Martin Kosek wrote:
On 12/11/2014 06:19 PM, Matt Chesler wrote:
I have a cluster of four IPA masters that should be performing fully
replication. I discovered yesterday that a recently created user
on a single master. After looking through all four masters, it
several recent updates only exist on one of the masters. I do not
replication errors in any of the logs, but I'm not 100% sure how far
That's really strange, because AFAIK, DS replication module yells
periodically if it cannot replicate so you should see it on the last
errors log page.
That should not occur. I remember a test case
(https://fedorahosted.org/389/ticket/47788) where a transient error
could conduct to an update being skipped.
Do you have access/errors logs since the missing entry was added.
Also would you dump the RUV on each of the masters (ldapsearch -D
"cn=directory manager" -w xxx -b "<your
Are you able to reproduce this problem ?
I do believe the one master with up-to-date data is a reliable
representation of what the LDAP directory should look like. I ran a
reinitialize command (ipa-replica-manage re-initialize --from
reliable-server.fqdn) on two of the out-of-date masters yesterday
EST. It's now a little after 12pm EST and the "Update in progress"
still scrolling by once a second on both terminals. I'd greatly
suggestions about a) how to determine the status of the reinitialize
and b) any other ideas about how to resolve this issue and monitor
better in the future. Thanks in advance for your help!
Thierry or Ludwig, any idea?
The replica agreement on the master should say when the total update is
completed. But after 12h it looks very long.
You may monitor the number of sent entries (grep -c
'2.16.840.1.1137188.8.131.52' <replica log>/access) to see if it progressing.
If it is not progressing for several minutes, would you get a pstack of
the master .
Manage your subscription for the Freeipa-users mailing list:
Go To http://freeipa.org for more info on the project