<div dir="ltr"><div>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><br></div><div>The VM isn't pingable and the liveliness check always fails.</div><div><br></div><div> <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)">ovirttest1</span><span style="color:rgb(0,0,0)">.<a href="http://wolfram.com">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=1
<br> metadata_feature_version=1
<br> timestamp=18980039 (Fri Nov 10 01:17:59 2017)
<br> host-id=1
<br> score=3400
<br> vm_conf_refresh_time=18980042 (Fri Nov 10 01:18:03 2017)
<br> conf_on_shared_storage=True
<br> maintenance=False
<br> state=GlobalMaintenance
<br> stopped=False<br>
<br></span><div><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><br clear="all"><div><div class="gmail_signature">Regards,<div>Logan Kuhn</div></div></div>
</div></div>