You where right.
I was able to start it manually but its still doing the same thing
after I try to activate the server it fenced the server and send a
reboot... Here is the status:>
https://pastebin.com/xbXX8UBX
--
Fernando Fuentes
ffuentes(a)txweather.org
http://www.txweather.org
On Fri, Oct 13, 2017, at 11:00 AM, Dafna Ron wrote:
> this suggests that libvirt is down.
> can you please check libvirtd service status and get the log for it?>>
>
> Thanks,
> Dafna
>
> On 10/13/2017 04:48 PM, Fernando Fuentes wrote:
>> Team,
>>
>> I went to the log and capture the messages from when the host did
>> the update all the way down to the failure.>>>
>>
https://pastebin.com/AwP1gh5g
>>
>>
>> I hope that helps narrowing down the issue....
>> Ideas, thoughts, and comments are welcome!
>>
>> Regards,
>>
>> --
>> Fernando Fuentes
>> ffuentes(a)txweather.org
>>
http://www.txweather.org
>>
>>
>>
>> On Fri, Oct 13, 2017, at 10:03 AM, Fernando Fuentes wrote:
>>> Thanks for your reply.
>>>
>>> As requested I got this from the messages log:
>>>
>>>
https://pastebin.com/t0HRhvT9
>>>
>>> This one is from the host engine:
>>>
>>>
https://pastebin.com/8vji6MGs
>>>
>>> And this one is from the host vdsm:
>>>
>>>
https://pastebin.com/GgnqRvTE
>>>
>>> The funny part is that right when I did the update it seems that
>>> vdsm died and there is no log after the update.>>>>
>>> On the messages lo you can see the errors and the attempts of me
>>> trying to restart manually but it dies.>>>>
>>> Any ideas?
>>>
>>>
>>> --
>>> Fernando Fuentes
>>> ffuentes(a)txweather.org
>>>
http://www.txweather.org
>>>
>>>
>>>
>>> On Fri, Oct 13, 2017, at 01:42 AM, Tomas Jelinek wrote:
>>>> can you please provide some logs to the issue?
>>>> /var/log/ovirt-engine/engine.log from engine machine and
>>>> /var/log/vdsm/vdsm.log from the affected host would be great
>>>> start.>>>>>
>>>> thank you
>>>>
>>>> On Fri, Oct 13, 2017 at 2:47 AM, Fernando Fuentes
>>>> <ffuentes(a)darktcp.net> wrote:>>>>>> Hello Team,
>>>>>
>>>>> I updated one of my host on my cluster and after it finish and
>>>>> try to>>>>>> activate the host it quickly claimed
that the host was
>>>>> unresponsive and>>>>>> it fenced the host... Now
every time I try to activate the
>>>>> host it>>>>>> clames that is unresponsive and
proceeds to fence it... This was
>>>>> not>>>>>> happening before the update....
>>>>> The host is reachable with no problems nor issues...
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> Centos 7.4 x86_64 host.
>>>>> Attached is the vdsm log
>>>>>
>>>>> engine is oVirt Engine Version: 4.0.2.6-1.el7.centos
>>>>>
>>>>> Regards,
>>>>>
>>>>> --
>>>>> Fernando Fuentes ffuentes(a)txweather.org
http://www.txweather.org>>>>>>
_______________________________________________
>>>>> 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
>>
>>
>>
>> _______________________________________________ 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