[ovirt-users] MoM is failing!!!

[Erekle Magradze]

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 at 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 at 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 at ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20171016/ef0b4ca3/attachment.html>