On Fri, Nov 10, 2017 at 9:42 AM, Kasturi Narra wrote:
> Hello Logan,
>One reason the liveliness check fails is host cannot ping your hosted
> engine vm. you can try connecting to HE vm using remote-viewer
> vnc://hypervisor-ip:5900 and from the hosted-engine --vm-status
Following my answer, this is the bug you opened to track this issue right?
You said in comment #2 of that bug that all is well now. Should we
close the bug then?
On Fri, Nov 10, 2017 at 8:22 AM, Logan Kuhn
When i look at the hosted-engine --vm-status i see that vm is up but it
is health is bad. Can you try connecting to the vm using remote-viewer
using the command below ?
On Fri, Nov 10, 2017 at 12:52 PM, Logan Kuhn
One reason the liveliness check fails is host cannot ping your hosted
engine vm. you can try connecting to HE vm using remote-viewer
vnc://hypervisor-ip:5900 and from the hosted-engine --vm-status output
looks like the HE vm is up and running fine.
- Please check internal dns
On Fri, Apr 22, 2016 at 10:31 AM, Budur Nagaraju wrote:
> I have configured hosted engine with two hosts ,one of the hosted engine is
> down and unable to make it active .
> Is there anyways to fix the issue ? I have restarted ha-agent and ha-broker
> but no luck.
Mail list logo