<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi all<br>
</p>
<br>
<div class="moz-cite-prefix">On 01/11/2017 08:52 AM, Eyal Edri
wrote:<br>
</div>
<blockquote
cite="mid:CACuV_HpRk_wkfvdtJDdZ2sanvvCvb2RY8XSU-bHFCYvHA=0SgA@mail.gmail.com"
type="cite">
<div dir="ltr">Adding Tomas from Virt.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jan 10, 2017 at 10:54 AM, Piotr
Kliczewski <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:piotr.kliczewski@gmail.com" target="_blank">piotr.kliczewski@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On Tue, Jan 10, 2017 at 9:29 AM, Daniel Belenky
<<a moz-do-not-send="true"
href="mailto:dbelenky@redhat.com">dbelenky@redhat.com</a>>
wrote:<br>
> Hi all,<br>
><br>
> test-repo_ovirt_experimental_<wbr>master (link to
Jenkins) job failed on<br>
> basic_sanity scenario.<br>
> The job was triggered by <a moz-do-not-send="true"
href="https://gerrit.ovirt.org/#/c/69845/"
rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/c/<wbr>69845/</a><br>
><br>
> From looking at the logs, it seems that the reason is
VDSM.<br>
><br>
> In the VDSM log, i see the following error:<br>
><br>
> 2017-01-09 16:47:41,331 ERROR (JsonRpc
(StompReactor)) [vds.dispatcher] SSL<br>
> error receiving from <yajsonrpc.betterAsyncore.<wbr>Dispatcher
connected ('::1',<br>
> 34942, 0, 0) at 0x36b95f0>: unexpected eof
(betterAsyncore:119)<br>
</span></blockquote>
</div>
</div>
</blockquote>
<br>
Daniel, could you please remind me the jenkins link? I see something
suspicious on the Vdsm log.<br>
Most notably, Vdsm received SIGTERM. Is this expected and part of
the test?<br>
<br>
<blockquote
cite="mid:CACuV_HpRk_wkfvdtJDdZ2sanvvCvb2RY8XSU-bHFCYvHA=0SgA@mail.gmail.com"
type="cite">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">
><br>
<br>
</span>This issue means that the client closed connection
while vdsm was<br>
replying. It can happen at any time<br>
when the client is not nice with the connection. As you can
see the<br>
client connected locally '::1'.<br>
<span class=""><br>
><br>
> Also, when looking at the MOM logs, I see the the
following:<br>
><br>
> 2017-01-09 16:43:39,508 - mom.vdsmInterface - ERROR -
Cannot connect to<br>
> VDSM! [Errno 111] Connection refused<br>
><br>
<br>
</span>Looking at the log at this time vdsm had no open
socket.</blockquote>
</div>
</div>
<br>
</blockquote>
<br>
Correct, but IIRC we have a race on startup - that's the reason why
MOM retries to connect. After the new try, MOM seems to behave<br>
correctly:<br>
<br>
2017-01-09 16:44:05,672 - mom.RPCServer - INFO - ping()<br>
2017-01-09 16:44:05,673 - mom.RPCServer - INFO - getStatistics()<br>
<br>
<pre class="moz-signature" cols="72">--
Francesco Romani
Red Hat Engineering Virtualization R & D
IRC: fromani</pre>
</body>
</html>