<div dir="ltr">Hello Logan,<div><br></div><div> One reason the liveliness check fails is host cannot ping your hosted engine vm. you can try connecting to HE vm using <span style="background-color:transparent;color:inherit;font-family:Consolas,Monaco,"Andale Mono",monospace;font-size:inherit;white-space:pre-wrap">remote-viewer vnc://hypervisor-ip:5900 and from the hosted-engine --vm-status output looks like the HE vm is up and running fine.</span></div><div><br></div><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:1rem;color:rgb(37,37,37);font-family:Overpass,"Open Sans",Helvetica,sans-serif;font-size:16px"><li style="box-sizing:border-box">Please check internal dns setting like resolv.conf setting</li><li style="box-sizing:border-box">Can not resolve virtual host name or ip address.</li></ul><div><font color="#252525" face="Overpass, Open Sans, Helvetica, sans-serif"><span style="font-size:16px">Thanks</span></font></div><div><font color="#252525" face="Overpass, Open Sans, Helvetica, sans-serif"><span style="font-size:16px">kasturi</span></font></div><div><font color="#252525" face="Overpass, Open Sans, Helvetica, sans-serif"><span style="font-size:16px"><br></span></font></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 10, 2017 at 12:56 PM, Logan Kuhn <span dir="ltr"><<a href="mailto:support@jac-properties.com" target="_blank">support@jac-properties.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-size:12.8px">We lost the backend storage that hosts our self hosted engine tonight. We've recovered it and there was no data corruption on the volume containing the HE disk. However, when we try to start the HE it doesn't give an error, but it also doesn't start. </div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">The VM isn't pingable and the liveliness check always fails.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"> <span style="color:rgb(0,0,0);font-family:monospace">[root@ovirttest1 ~]# hosted-engine --vm-status | grep -A20 ovirttest1 </span></div><span style="font-family:monospace">Hostname : <span style="font-weight:bold;color:rgb(255,84,84)">ov<wbr>irttest1</span><span style="color:rgb(0,0,0)">.<a href="http://wolfram.com/" target="_blank">wolfram.com</a> </span><br>Host ID : 1 <br>Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "up"} <br>Score : 3400 <br>stopped : False <br>Local maintenance : False <br>crc32 : 2c2f3ec9 <br>local_conf_timestamp : 18980042 <br>Host timestamp : 18980039 <br>Extra metadata (valid at timestamp): <br> metadata_parse_version=<wbr>1 <br> metadata_feature_versio<wbr>n=1 <br> timestamp=18980039 (Fri Nov 10 01:17:59 2017) <br> host-id=1 <br> score=3400 <br> vm_conf_refresh_time=18<wbr>980042 (Fri Nov 10 01:18:03 2017) <br> conf_on_shared_storage=<wbr>True <br> maintenance=False <br> state=<wbr>GlobalMaintenance <br> stopped=False<br><br></span><div style="font-size:12.8px"><span style="font-family:monospace">The environment is in Global Maintenance so that we can isolate it to starting on a specific host to eliminate as many variables as possible. I've attached the agent and broker logs<br></span></div>
</div>
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>