This is a multi-part message in MIME format.
--------------19FBF4BCBBA63BEF231F366A
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
It's was a typo in the failure message,
that's what I was getting:
*VDSM hostname command GetStatsVDS failed: Connection reset by peer*
On 10/16/2017 03:21 PM, Erekle Magradze wrote:
Hi,
It's getting clear now, indeed momd service is disabled
● momd.service - Memory Overcommitment Manager Daemon
Loaded: loaded (/usr/lib/systemd/system/momd.service; static;
vendor preset: disabled)
Active: inactive (dead)
mom-vdsm is enable and running.
● mom-vdsm.service - MOM instance configured for VDSM purposes
Loaded: loaded (/usr/lib/systemd/system/mom-vdsm.service; enabled;
vendor preset: enabled)
Active: active (running) since Mon 2017-10-16 15:14:35 CEST; 1min
3s ago
Main PID: 27638 (python)
CGroup: /system.slice/mom-vdsm.service
└─27638 python /usr/sbin/momd -c /etc/vdsm/mom.conf
The reason why I came up with digging in mom problems is the following
problem
*VDSM hostname command GetStatsVDSThanks failed: Connection reset by peer*
that is causing fencing of the node where the failure is happening,
what could be the reason of GetStatsVDS failure?
Best Regards
Erekle
On 10/16/2017 03:11 PM, Martin Sivak wrote:
> 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
> <erekle.magradze(a)recogizer.de> wrote:
>> 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:
>>> 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
>>> <erekle.magradze(a)recogizer.de> wrote:
>>>> 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
>>>> Users(a)ovirt.org
>>>>
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Recogizer Group GmbH
Dr.rer.nat. Erekle Magradze
Lead Big Data Engineering & DevOps
Rheinwerkallee 2, 53227 Bonn
Tel: +49 228 29974555
E-Mail erekle.magradze(a)recogizer.de
Web:
www.recogizer.com
Recogizer auf LinkedIn
https://www.linkedin.com/company-beta/10039182/
Folgen Sie uns auf Twitter
https://twitter.com/recogizer
-----------------------------------------------------------------
Recogizer Group GmbH
Geschäftsführer: Oliver Habisch, Carsten Kreutze
Handelsregister: Amtsgericht Bonn HRB 20724
Sitz der Gesellschaft: Bonn; USt-ID-Nr.: DE294195993
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und löschen Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail und der darin
enthaltenen Informationen ist nicht gestattet.
--------------19FBF4BCBBA63BEF231F366A
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>It's was a typo in the failure message, </p>
<p>that's what I was getting:<br>
</p>
<p><b>VDSM hostname command GetStatsVDS failed: Connection reset by
peer</b></p>
<br>
<div class="moz-cite-prefix">On 10/16/2017 03:21 PM, Erekle Magradze
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:06f6522c-44ba-9b3f-384d-a4a56a59a6ff@recogizer.de">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<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"
moz-do-not-send="true">&lt;erekle.magradze(a)recogizer.de&gt;</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"
moz-do-not-send="true">&lt;erekle.magradze(a)recogizer.de&gt;</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"
moz-do-not-send="true">Users(a)ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users"
moz-do-not-send="true">http://lists.ovirt.org/mailman/listin...
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
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://...
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Recogizer Group GmbH
Dr.rer.nat. Erekle Magradze
Lead Big Data Engineering & DevOps
Rheinwerkallee 2, 53227 Bonn
Tel: +49 228 29974555
E-Mail <a class="moz-txt-link-abbreviated"
href="mailto:erekle.magradze@recogizer.de">erekle.magradze@recogizer.de</a>
Web: <a class="moz-txt-link-abbreviated"
href="http://www.recogizer.com">www.recogizer.com</a>
Recogizer auf LinkedIn <a class="moz-txt-link-freetext"
href="https://www.linkedin.com/company-beta/10039182/">https...
Folgen Sie uns auf Twitter <a class="moz-txt-link-freetext"
href="https://twitter.com/recogizer">https://twitter.com/rec...
-----------------------------------------------------------------
Recogizer Group GmbH
Geschäftsführer: Oliver Habisch, Carsten Kreutze
Handelsregister: Amtsgericht Bonn HRB 20724
Sitz der Gesellschaft: Bonn; USt-ID-Nr.: DE294195993
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und löschen Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail und der darin
enthaltenen Informationen ist nicht gestattet.</pre>
</body>
</html>
--------------19FBF4BCBBA63BEF231F366A--