<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi,</p>
<p>It's getting clear now, indeed momd service is disabled</p>
<p>● momd.service - Memory Overcommitment Manager Daemon<br>
Loaded: loaded (/usr/lib/systemd/system/momd.service; static;
vendor preset: disabled)<br>
Active: inactive (dead)</p>
<p>mom-vdsm is enable and running.<br>
</p>
<p>● mom-vdsm.service - MOM instance configured for VDSM purposes<br>
Loaded: loaded (/usr/lib/systemd/system/mom-vdsm.service;
enabled; vendor preset: enabled)<br>
Active: active (running) since Mon 2017-10-16 15:14:35 CEST;
1min 3s ago<br>
Main PID: 27638 (python)<br>
CGroup: /system.slice/mom-vdsm.service<br>
└─27638 python /usr/sbin/momd -c /etc/vdsm/mom.conf<br>
<br>
The reason why I came up with digging in mom problems is the
following problem<br>
</p>
<br>
<b>VDSM hostname command GetStatsVDSThanks failed: Connection reset
by peer</b><br>
<br>
that is causing fencing of the node where the failure is happening,
what could be the reason of GetStatsVDS failure?<br>
<br>
Best Regards<br>
Erekle<br>
<br>
<br>
<div class="moz-cite-prefix">On 10/16/2017 03:11 PM, Martin Sivak
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAF0zDV4VRC3zj4TYtfiHREFB7AxEN8Fj6fFwZN7MMk-mZQMHEA@mail.gmail.com">
<pre wrap="">Hi,
how do you start MOM? MOM is supposed to talk to vdsm, we do not talk
to libvirt directly. The line you posted comes from vdsm and vdsm is
telling you it can't talk to MOM.
Which MOM service is enabled? Because there are two momd and mom-vdsm,
the second one is the one that should be enabled.
Best regards
Martin Sivak
On Mon, Oct 16, 2017 at 3:04 PM, Erekle Magradze
<a class="moz-txt-link-rfc2396E" href="mailto:erekle.magradze@recogizer.de"><erekle.magradze@recogizer.de></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Martin,
Thanks for the answer, unfortunately this warning message persists, does it
mean that mom cannot communicate with libvirt? how critical is it?
Best
Erekle
On 10/16/2017 03:03 PM, Martin Sivak wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Hi,
it is just a warning, there is nothing you have to solve unless it
does not resolve itself within a minute or so. If it happens only once
or twice after vdsm or mom restart then you are fine.
Best regards
--
Martin Sivak
SLA / oVirt
On Mon, Oct 16, 2017 at 2:44 PM, Erekle Magradze
<a class="moz-txt-link-rfc2396E" href="mailto:erekle.magradze@recogizer.de"><erekle.magradze@recogizer.de></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Hi,
after running
systemctl status vdsm I am getting that it's running and this message at
the
end.
Oct 16 14:26:52 hostname vdsmd[2392]: vdsm throttled WARN MOM not
available.
Oct 16 14:26:52 hostname vdsmd[2392]: vdsm throttled WARN MOM not
available,
KSM stats will be missing.
Oct 16 14:26:57 hostname vdsmd[2392]: vdsm root WARN ping was deprecated
in
favor of ping2 and confirmConnectivity
how critical it is? and how to solve that warning?
I am using libvirt
Cheers
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br>
</body>
</html>