<div dir="ltr"><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Does anyone have any clues about these errors?<br><div><br></div><div><br><div><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Sat, Apr 7, 2018 at 9:02 PM, Vincent Royer <span dir="ltr"><<a href="mailto:vincent@epicenergy.ca" target="_blank">vincent@epicenergy.ca</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>Suffered a long power outage that outlasted our huge UPS, so both my nodes went down. </div><div><br></div><div>Upon return, the nodes came back up but engine did not start because the storage server takes longer to boot than the nodes do, so the NFS mounts didn't reconnect. </div><div><br></div><div>I manually re-entered the mounts using cockpit, rebooted the nodes and the engine came back up along with all VMs. </div><div><br></div><div>Now in cockpit under Node Status, It says Health: bad, and these messages:</div><div><br></div><div><img src="cid:ii_jfq9lsjd0_162a35b917c160dc" width="350" height="255" style="margin-right:0px"></div><div><br></div><div>Everything seems to be working fine though. <br><br></div>
</div>
</blockquote></div><br></div></div>