<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello James,<br>
<br>
The fact that the master is more powerfull than the replica
increase the possibility to hit that bug.<br>
The bug fix is on the master side. The master is made smarter to
adapt its replication flow to the speed of the consumer.<br>
The bug is fixed in 389-ds-base-1.3.3.1-10.el7 and
389-ds-base-1.2.11.15-56.el6.<br>
<br>
What is the current version of your master ?<br>
<br>
thanks<br>
thierry<br>
On 06/08/2015 09:49 AM, James James wrote:<br>
</div>
<blockquote
cite="mid:CALBJVV=1HT0TuAW9YbWtFCKeWECG4uGHG9zPT5ypab0NqdUMTA@mail.gmail.com"
type="cite">
<div dir="ltr">Hi Thierry,
<div><br>
</div>
<div>thanks for you answer.</div>
<div><br>
</div>
<div>I was away for a long time, this is why my post comes later
. </div>
<div><br>
</div>
<div>This timing issue is coming when you try to upgrade from
rhel 6 (ipa-3.0) to rhel7 (ipa4.xx) ? </div>
<div><br>
</div>
<div>
<div>I have a physical machine for the master and a VM as
replica. The solution is to use a physical machine for the
replica ? </div>
</div>
<div><br>
</div>
<div>How can I limit the cpu/memory in the physical machine
(with cgroups ??).</div>
<div><br>
</div>
<div>Any hints will be appreciated ..</div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>James</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-05-18 14:04 GMT+02:00 thierry
bordaz <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:tbordaz@redhat.com" target="_blank">tbordaz@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<div>On 05/15/2015 05:11 PM, James James wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>ok Rob. Thanks for your help. I will wait for
the Scientific Linux 6.7 .<br>
</div>
</div>
</div>
</blockquote>
<br>
</span> Hi James,<br>
<br>
Unfortunately there is no workaround. This is a timing
issue mostly seen when the master is more powerful than
the consumer.<br>
If you are using VM you may try to get master/replica with
nearly the same cpu/memory.<br>
<br>
thanks<span class="HOEnZb"><font color="#888888"><br>
thierry</font></span>
<div>
<div class="h5"><br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div><br>
</div>
Best.<br>
<br>
</div>
James<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-05-15 16:58
GMT+02:00 Rich Megginson <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:rmeggins@redhat.com"
target="_blank">rmeggins@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span>
<div>On 05/15/2015 08:46 AM, James James
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">[root@ipa ~]# rpm -q
389-ds-base<br>
389-ds-base-1.2.11.15-50.el6_6.x86_64<br>
</div>
</blockquote>
<br>
</span> Ok. Looks like this is planned to
be fixed in RHEL 6.7 with version
389-ds-base-1.2.11.15-56.el6<br>
<br>
I don't know if there are any workarounds.
<div>
<div><br>
<br>
<blockquote type="cite">
<div dir="ltr"><br>
<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-05-15
16:32 GMT+02:00 Rich Megginson <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:rmeggins@redhat.com"
target="_blank">rmeggins@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div bgcolor="#FFFFFF"
text="#000000"><span>
<div>On 05/15/2015 08:22 AM,
James James wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>I think that : <br>
<br>
<span><span>Starting
replication,
please wait
until this has
completed.<br>
<span>Update</span>
in progress, 127
seconds elapsed<br>
<span>Update</span>
in progress yet
not in progress<br>
<br>
</span></span></div>
<span><span><br>
</span></span></div>
<span><span>looks like a
time error : <a
moz-do-not-send="true"
href="https://fedorahosted.org/freeipa/ticket/4756" target="_blank">https://fedorahosted.org/freeipa/ticket/4756</a><br>
</span></span></div>
</blockquote>
<br>
</span> That issue should have
been fixed in
389-ds-base-1.3.3 branch.
What version of 389-ds-base?
rpm -q 389-ds-base
<div>
<div><br>
<br>
<blockquote type="cite">
<div class="gmail_extra"><br>
<div
class="gmail_quote">2015-05-15
16:00 GMT+02:00 Rich
Megginson <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:rmeggins@redhat.com" target="_blank">rmeggins@redhat.com</a>></span>:<br>
<blockquote
class="gmail_quote"
style="margin:0 0
0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex">
<div
bgcolor="#FFFFFF"
text="#000000"><span>
<div>On
05/15/2015
07:55 AM,
James James
wrote:<br>
</div>
<blockquote
type="cite">
<div dir="ltr">Is
it possible to
change the <font
face="Times
New Roman,
Times, serif">nsds5ReplicaTimeout
value to get
rid of this
timeout <span>error</span>
?</font></div>
</blockquote>
<br>
</span><font
face="Times
New Roman,
Times, serif">What
timeout error?<br>
<br>
</font>
<div>
<div>
<blockquote
type="cite">
<div
class="gmail_extra"><br>
<div
class="gmail_quote">2015-04-17
4:52 GMT+02:00
Rich Megginson
<span
dir="ltr"><<a
moz-do-not-send="true" href="mailto:rmeggins@redhat.com" target="_blank">rmeggins@redhat.com</a>></span>:<br>
<blockquote
class="gmail_quote"
style="margin:0
0 0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex">
<div
bgcolor="#FFFFFF"
text="#000000"><span>
<div>On
04/15/2015
10:44 PM,
James James
wrote:<br>
</div>
<blockquote
type="cite">
<div dir="ltr">The
ipareplica-install.log
file in
attachment ...
</div>
</blockquote>
<br>
</span> Here
are the
pertinent
bits:<br>
<br>
2015-04-15T15:06:31Z
DEBUG
wait_for_open_ports:
localhost
[389] timeout
300<br>
2015-04-15T15:06:32Z
DEBUG flushing
<a
moz-do-not-send="true">ldap://ipa.example.com:389</a>
from
SchemaCache<br>
2015-04-15T15:06:32Z
DEBUG
retrieving
schema for
SchemaCache
url=<a
moz-do-not-send="true">ldap://ipa.example.com:389</a>
conn=<ldap.ldapobject.SimpleLDAPObject
instance at
0x484f4d0><br>
2015-04-15T15:06:32Z
DEBUG flushing
<a
moz-do-not-send="true">ldaps://ipa1.example.com:636</a>
from
SchemaCache<br>
2015-04-15T15:06:32Z
DEBUG
retrieving
schema for
SchemaCache
url=<a
moz-do-not-send="true">ldaps://ipa1.example.com:636</a>
conn=<ldap.ldapobject.SimpleLDAPObject
instance at
0x4170290><br>
2015-04-15T15:08:44Z
DEBUG
Traceback
(most recent
call last):<br>
File
"/usr/lib/python2.7/site-packages/ipaserver/install/service.py",
line 382, in
start_creation<br>
run_step(full_msg,
method)<br>
File
"/usr/lib/python2.7/site-packages/ipaserver/install/service.py",
line 372, in
run_step<br>
method()<br>
File
"/usr/lib/python2.7/site-packages/ipaserver/install/dsinstance.py",
line 368, in
__setup_replica<br>
r_bindpw=self.dm_password)<br>
File
"/usr/lib/python2.7/site-packages/ipaserver/install/replication.py",
line 969, in
setup_replication<br>
raise
RuntimeError("Failed
to start
replication")<span><br>
RuntimeError:
Failed to
start
replication<br>
<br>
</span>
2015-04-15T15:08:44Z
DEBUG
[error]
RuntimeError:
Failed to
start
replication<br>
<br>
The times are
a little off,
but I believe
this
corresponds to<span><br>
[15/Apr/2015:17:08:39
+0200] -
import
userRoot:
Import
complete.
Processed 1539
entries in 126
seconds.
(12.21
entries/sec)<br>
[15/Apr/2015:17:08:39
+0200]
NSMMReplicationPlugin
-
multimaster_be_state_change:
replica
dc=lix,dc=polytechnique,dc=fr
is coming
online;
enabling
replication<br>
<br>
</span> I
don't know why
setup_replication
is reporting
an error if
replication
completed
successfully.
<div>
<div><br>
<br>
<blockquote
type="cite">
<div
class="gmail_extra"><br>
<div
class="gmail_quote">2015-04-16
2:22 GMT+02:00
Rob Crittenden
<span
dir="ltr"><<a
moz-do-not-send="true" href="mailto:rcritten@redhat.com" target="_blank">rcritten@redhat.com</a>></span>:<br>
<blockquote
class="gmail_quote"
style="margin:0
0 0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex"><span>Rich
Megginson
wrote:<br>
> On
04/15/2015
02:58 PM,
James James
wrote:<br>
>>
Nothing on the
replica ..
maybye a
process on the
master. How
can I<br>
>> check
that ?<br>
><br>
> I have no
idea. But it
seems highly
unlikely that
a process on
the<br>
> master is
able to
shutdown a
process on the
replica . . .<br>
><br>
> I would
say that there
is some
problem with
the
ipa-replica-install
not<br>
> properly
checking the
status - see
below:<br>
><br>
>><br>
>>
2015-04-15
21:37
GMT+02:00 Rich
Megginson <<a
moz-do-not-send="true" href="mailto:rmeggins@redhat.com" target="_blank">rmeggins@redhat.com</a><br>
</span>>>
<mailto:<a
moz-do-not-send="true" href="mailto:rmeggins@redhat.com" target="_blank">rmeggins@redhat.com</a>>>:<br>
<span>>><br>
>>
On 04/15/2015
12:43 PM,
James James
wrote:<br>
>>>
Here the
log<br>
>>><br>
>>>
2015-04-15
18:58
GMT+02:00 Rich
Megginson <<a
moz-do-not-send="true" href="mailto:rmeggins@redhat.com" target="_blank">rmeggins@redhat.com</a><br>
</span>>>>
<mailto:<a
moz-do-not-send="true" href="mailto:rmeggins@redhat.com" target="_blank">rmeggins@redhat.com</a>>>:<br>
<span>>>><br>
>>>
On
04/15/2015
09:46 AM,
James James
wrote:<br>
>>>>
Hello,<br>
>>>><br>
>>>>
I have
been looking
to solve my
problem but I
'm asking for<br>
>>>>
some
help.<br>
>>>><br>
>>>>
The
replication
begins but
cannot be
completed ....<br>
>>>><br>
>>>>
I want
to install a
new fresh
replica but
I've always
got<br>
>>>>
this
error :<br>
>>>><br>
>>>>
[21/35]:
configure
dirsrv ccache<br>
>>>>
[22/35]:
enable SASL
mapping
fallback<br>
>>>>
[23/35]:
restarting
directory
server<br>
>>>>
[24/35]:
setting up
initial
replication<br>
>>>>
Starting
replication,
please wait
until this has
completed.<br>
>>>>
Update
in progress,
127 seconds
elapsed<br>
>>>>
Update
in progress
yet not in
progress<br>
>>>><br>
>>>>
Update
in progress
yet not in
progress<br>
>>><br>
><br>
> in
progress yet
not in
progress????
The error log
below clearly
shows<br>
> that
replica init
succeeded
after 127
seconds.<br>
><br>
> IPA-ers -
wasn't there
some bug about
checking
replica status
properly?<br>
><br>
<br>
</span>The
loop looks at
nsds5BeginReplicaRefresh,
nsds5replicaUpdateInProgress<br>
and
nsds5ReplicaLastInitStatus.<br>
<br>
It loops
looking for
nsds5BeginReplicaRefresh.
If there is no
value it<br>
prints "Update
in progress,
%d seconds
elapsed". Once
it gets a
status,<br>
the update is
done, and it
looks at
nsds5ReplicaLastInitStatus.
If it<br>
isn't empty,
doesn't
include
'replica busy'
or 'Total
update
succeeded'<br>
then it looks
to see if
nsds5replicaUpdateInProgress
is TRUE. If it
is,<br>
ir prints
Update in
progress yet
not in
progress and
tries the loop
again.<br>
<br>
AFAICT this
part of a
replica
install
doesn't
restart
389-ds.<br>
<br>
/var/log/ipareplica-install.log
may hold some
details.<br>
<span><font
color="#888888"><br>
rob<br>
<br>
</font></span></blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>