<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 18 Nov 2016, at 12:12, Oved Ourfali <<a href="mailto:oourfali@redhat.com" class="">oourfali@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p dir="ltr" class="">I don't think it is related to version X or Y. It is a race, so might be related to other factors. </p></div></blockquote><div><br class=""></div>likely because json-rpc is initialized after xml-rpc….or indeed whatever else;-)</div><div><br class=""></div><div>either way it needs to be solved. Either by improving the systemd service file or mom retry (btw you likely still want to have a retry in mom once it starts responding due to delayed vdsm async recovery taking potentially minutes)</div><div><br class=""><blockquote type="cite" class=""><div class="">
<div class="gmail_extra"><br class=""><div class="gmail_quote">On Nov 18, 2016 12:59 PM, "Martin Sivak" <<a href="mailto:msivak@redhat.com" class="">msivak@redhat.com</a>> wrote:<br type="attribution" class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> Are we / can we use systemd socket activation there?<br class="">
<br class="">
That actually requires systemd specific code iirc (to take over the<br class="">
standing by socket). I am actually wondering why the xml-rpc in 4.0.4<br class="">
was fine and json-rpc in 4.0.6 is too slow.<br class="">
<br class="">
Martin<br class="">
<br class="">
On Fri, Nov 18, 2016 at 11:53 AM, Anton Marchukov <<a href="mailto:amarchuk@redhat.com" class="">amarchuk@redhat.com</a>> wrote:<br class="">
> Hello All.<br class="">
><br class="">
> Are we / can we use systemd socket activation there?<br class="">
><br class="">
> Anton.<br class="">
><br class="">
> On Fri, Nov 18, 2016 at 11:21 AM, Martin Sivak <<a href="mailto:msivak@redhat.com" class="">msivak@redhat.com</a>> wrote:<br class="">
>><br class="">
>> What about making vdsm ready to answer connections when it returns to<br class="">
>> systemd instead? I hate workarounds and this always worked fine.<br class="">
>><br class="">
>> Martin<br class="">
>><br class="">
>> On Fri, Nov 18, 2016 at 11:13 AM, Oved Ourfali <<a href="mailto:oourfali@redhat.com" class="">oourfali@redhat.com</a>><br class="">
>> wrote:<br class="">
>> > Seems like a race regardless of the protocol.<br class="">
>> > Should you add a retry?<br class="">
>> ><br class="">
>> ><br class="">
>> > On Nov 18, 2016 11:52 AM, "Martin Sivak" <<a href="mailto:msivak@redhat.com" class="">msivak@redhat.com</a>> wrote:<br class="">
>> >><br class="">
>> >> Yes, because VDSM is supposed to be up (there is systemd dependency).<br class="">
>> >> This always worked fine with xml-rpc.<br class="">
>> >><br class="">
>> >> Martin<br class="">
>> >><br class="">
>> >> On Fri, Nov 18, 2016 at 10:14 AM, Nir Soffer <<a href="mailto:nsoffer@redhat.com" class="">nsoffer@redhat.com</a>><br class="">
>> >> wrote:<br class="">
>> >> > On Fri, Nov 18, 2016 at 10:45 AM, Martin Sivak <<a href="mailto:msivak@redhat.com" class="">msivak@redhat.com</a>><br class="">
>> >> > wrote:<br class="">
>> >> >> This happens because MOM can't connect to VDSM and so it quits.<br class="">
>> >> ><br class="">
>> >> > So mom try once to connect and if the connection fails it quits?<br class="">
>> >> ><br class="">
>> >> >> We<br class="">
>> >> >> discussed it on the mailinglist<br class="">
>> >> >><br class="">
>> >> >><br class="">
>> >> >><br class="">
>> >> >> <a href="https://lists.fedoraproject.org/archives/list/vdsm-devel@lists.fedorahosted.org/thread/MZ7UJUWO5KFRDJJDNXX7VIYU5PWSXF62/" rel="noreferrer" target="_blank" class="">https://lists.fedoraproject.<wbr class="">org/archives/list/vdsm-devel@<wbr class="">lists.fedorahosted.org/thread/<wbr class="">MZ7UJUWO5KFRDJJDNXX7VIYU5PWSXF<wbr class="">62/</a><br class="">
>> >> >> <a href="http://lists.ovirt.org/pipermail/devel/2016-November/014101.html" rel="noreferrer" target="_blank" class="">http://lists.ovirt.org/<wbr class="">pipermail/devel/2016-November/<wbr class="">014101.html</a><br class="">
>> >> >><br class="">
>> >> >> This issue never happened with XML-RPC.<br class="">
>> >> >><br class="">
>> >> >> Shira reported it as<br class="">
>> >> >> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1393012" rel="noreferrer" target="_blank" class="">https://bugzilla.redhat.com/<wbr class="">show_bug.cgi?id=1393012</a><br class="">
>> >> >><br class="">
>> >> >> Martin<br class="">
>> >> >><br class="">
>> >> >> On Thu, Nov 17, 2016 at 7:42 PM, Yaniv Kaul <<a href="mailto:ykaul@redhat.com" class="">ykaul@redhat.com</a>><br class="">
>> >> >> wrote:<br class="">
>> >> >>> I've recently seen, including now on Master, the following<br class="">
>> >> >>> warnings:<br class="">
>> >> >>> Nov 17 13:33:25 lago-basic-suite-master-host0 systemd[1]: Started<br class="">
>> >> >>> MOM<br class="">
>> >> >>> instance configured for VDSM purposes.<br class="">
>> >> >>> Nov 17 13:33:25 lago-basic-suite-master-host0 systemd[1]: Starting<br class="">
>> >> >>> MOM<br class="">
>> >> >>> instance configured for VDSM purposes...<br class="">
>> >> >>> Nov 17 13:33:35 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available, Policy could not be set.<br class="">
>> >> >>> Nov 17 13:33:39 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available.<br class="">
>> >> >>> Nov 17 13:33:39 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available, KSM stats will be missing.<br class="">
>> >> >>> Nov 17 13:33:55 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available.<br class="">
>> >> >>> Nov 17 13:33:55 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available, KSM stats will be missing.<br class="">
>> >> >>> Nov 17 13:34:10 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available.<br class="">
>> >> >>> Nov 17 13:34:10 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available, KSM stats will be missing.<br class="">
>> >> >>> Nov 17 13:34:26 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available.<br class="">
>> >> >>> Nov 17 13:34:26 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available, KSM stats will be missing.<br class="">
>> >> >>> Nov 17 13:34:42 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available.<br class="">
>> >> >>> Nov 17 13:34:42 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available, KSM stats will be missing.<br class="">
>> >> >>> Nov 17 13:34:57 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available.<br class="">
>> >> >>> Nov 17 13:34:57 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available, KSM stats will be missing.<br class="">
>> >> >>> Nov 17 13:35:12 lago-basic-suite-master-host0 vdsm[2012]: vdsm MOM<br class="">
>> >> >>> WARN MOM<br class="">
>> >> >>> not available.<br class="">
>> >> >>><br class="">
>> >> >>><br class="">
>> >> >>><br class="">
>> >> >>> Any ideas what this is and why?<br class="">
>> >> >>><br class="">
>> >> >>> ______________________________<wbr class="">_________________<br class="">
>> >> >>> Devel mailing list<br class="">
>> >> >>> <a href="mailto:Devel@ovirt.org" class="">Devel@ovirt.org</a><br class="">
>> >> >>> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank" class="">http://lists.ovirt.org/<wbr class="">mailman/listinfo/devel</a><br class="">
>> >> >> ______________________________<wbr class="">_________________<br class="">
>> >> >> Devel mailing list<br class="">
>> >> >> <a href="mailto:Devel@ovirt.org" class="">Devel@ovirt.org</a><br class="">
>> >> >> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank" class="">http://lists.ovirt.org/<wbr class="">mailman/listinfo/devel</a><br class="">
>> >> ______________________________<wbr class="">_________________<br class="">
>> >> Devel mailing list<br class="">
>> >> <a href="mailto:Devel@ovirt.org" class="">Devel@ovirt.org</a><br class="">
>> >> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank" class="">http://lists.ovirt.org/<wbr class="">mailman/listinfo/devel</a><br class="">
>> >><br class="">
>> >><br class="">
>> ><br class="">
>> ______________________________<wbr class="">_________________<br class="">
>> Devel mailing list<br class="">
>> <a href="mailto:Devel@ovirt.org" class="">Devel@ovirt.org</a><br class="">
>> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank" class="">http://lists.ovirt.org/<wbr class="">mailman/listinfo/devel</a><br class="">
><br class="">
><br class="">
><br class="">
><br class="">
> --<br class="">
> Anton Marchukov<br class="">
> Senior Software Engineer - RHEV CI - Red Hat<br class="">
><br class="">
</blockquote></div></div>
_______________________________________________<br class="">Devel mailing list<br class=""><a href="mailto:Devel@ovirt.org" class="">Devel@ovirt.org</a><br class="">http://lists.ovirt.org/mailman/listinfo/devel</div></blockquote></div><br class=""></body></html>