<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 31, 2017 at 3:23 PM, George Mcro <span dir="ltr"><<a href="mailto:george.mcro@experia.gr" target="_blank">george.mcro@experia.gr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="direction:ltr;font-family:Tahoma;color:#000000;font-size:10pt">
<p class="MsoNormal"><span lang="EN-US">Hello,</span></p>
<p class="MsoNormal"><span lang="EN-US">My infrastructure consist of 2 ovirt-nodes and one ovirt-engine. All of them use Centos 7.</span></p>
<p class="MsoNormal"><span lang="EN-US">I have already configured Ovirt-Engine and both of ovirt-nodes. Before I install the two ovirt-nodes in Ovirt engine, I install this repo in both of them
</span><span style="font-family:Wingdings" lang="EN-US">à</span><span lang="EN-US"> yum install
<a href="http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm" target="_blank">http://resources.ovirt.org/<wbr>pub/yum-repo/ovirt-release41.<wbr>rpm</a>.</span></p>
<p class="MsoNormal"><span lang="EN-US">I want to clarify that the ovirt engine is HP proliant DL380 G6 and the 2 ovirt nodes are HP Proliant DL380G7. Also, the ovirt-node servers are hardware identical(same motherboard, same
HP model, same NIC’s etc).</span></p>
<p class="MsoNormal"><span lang="EN-US">Now, the issue.</span></p>
<p class="MsoNormal"><span lang="EN-US">Ovirt-Node no2(hype02) operates perfectly for days with 4 VM’s on it. But, when I am migrating vm’s from ovirt-Node no2 (hype02) to ovirt-Node no1 (hype01) to see if it is capable to operate
like hype02, it restarts after couple of hours (2-4).</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Ovirt engine event logs report :
</span></p>
<p class="MsoNormal"><span lang="EN-US">VDSM hype01 command GetStatsVDS failed: Heartbeat exceeded (hype01).</span></p>
<p class="MsoNormal"><span lang="EN-US"> <wbr> <wbr> Or</span></p>
<p class="MsoNormal"><span lang="EN-US">VDSM hype01 command GetStatsVDS failed: Connection issue java.rmi.ConnectException: Connection timeout</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">I have done almost every change I could think of. I reinstall Centos 7 couple of times, upgrade BIOS and iLO in the latest version. Moreover, I changed Hard Drives (with the same HP Model),
Motherboard, and RAMs but nothing worked.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Then, I tried something else. I put the server in Maintenance mode and voila, it was operating for 4 days straight without restarting.</span></p></div></div></blockquote><div><br></div><div>Could it be unrelated HW? Your network connection (switch) for example is flapping? Anything on the storage?</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="direction:ltr;font-family:Tahoma;color:#000000;font-size:10pt">
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">So, I do not know what it’s wrong and logs sadly do not help me understand.</span></p>
<p class="MsoNormal"><span lang="EN-US">I will post here some log files, dmesg, messages, supervdsm and vdsm.
</span></p>
<p class="MsoNormal"><span lang="EN-US">Any ideas what’s the issue here. Hardware or Software. Any help would be appreciated.</span></p>
<p class="MsoNormal"><span lang="EN-US"><br>
</span></p>
<p class="MsoNormal"><span lang="EN-US">King Regards,</span></p>
<p class="MsoNormal"><span lang="EN-US">George Mcro<br>
</span></p>
</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></div>