<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Feb 20, 2017 10:48 PM, &quot;cmc&quot; &lt;<a href="mailto:iucounu@gmail.com">iucounu@gmail.com</a>&gt; wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Due to networking and DNS issues. our engine was offlined (it is<br>
physical machine currently, will be converting it to a VM in the<br>
future when time allows). When service was restored, I noticed that<br>
all the VMs were listed as being in an unknown state on one host. The<br>
VMs were fine, but the engine could not ascertain their status as the<br>
host itself was in an unknown state. vdsm was reporting errors and was<br>
not running on the engine (or at least was in status &#39;failed&#39; in<br>
systemd). I tried starting vdsmd on the engine but it would not start.<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">VDSM should not be running on the engine. </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I decided to try to restart vdsmd on the host and that did allow the<br>
state of the VMs to be discovered, and the engine listed the host as<br>
up again. However, there are still errors with vdsmd on both the host<br>
and the engine, and the engine cannot start vdsmd. I guess it is able<br>
to monitor the hosts in a limited way as it says they are both up.<br>
There are communication errors between one of the hosts and the<br>
engine: the host is refusing connections by the look of it<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">Is iptables / firewalld set up correctly? </div><div dir="auto">Y. </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
from the engine log:<br>
<br>
2017-02-20 18:41:51,226Z ERROR<br>
[org.ovirt.engine.core.<wbr>vdsbroker.vdsbroker.<wbr>GetCapabilitiesVDSCommand]<br>
(DefaultQuartzScheduler2) [f8aa18b3-97b9-48e2-a681-<wbr>cf3aaed330a5]<br>
Command &#39;GetCapabilitiesVDSCommand(<wbr>HostName = k<br>
vm-ldn-01, VdsIdAndVdsVDSCommandParameter<wbr>sBase:{runAsync=&#39;true&#39;,<br>
hostId=&#39;e050c27f-8709-404c-<wbr>b03e-59c0167a824b&#39;,<br>
vds=&#39;Host[kvm-ldn-01,e050c27f-<wbr>8709-404c-b03e-59c0167a824b]&#39;}<wbr>)&#39;<br>
execution failed: java.net.ConnectExce<br>
ption: Connection refused<br>
2017-02-20 18:41:51,226Z ERROR<br>
[org.ovirt.engine.core.<wbr>vdsbroker.monitoring.<wbr>HostMonitoring]<br>
(DefaultQuartzScheduler2) [f8aa18b3-97b9-48e2-a681-<wbr>cf3aaed330a5]<br>
Failure to refresh host &#39;kvm-ldn-01&#39; runtime info: java.n<br>
et.ConnectException: Connection refused<br>
2017-02-20 18:41:52,772Z ERROR<br>
[org.ovirt.engine.core.<wbr>vdsbroker.vdsbroker.<wbr>GetAllVmStatsVDSCommand]<br>
(DefaultQuartzScheduler6) [f8aa18b3-97b9-48e2-a681-<wbr>cf3aaed330a5]<br>
Command &#39;GetAllVmStatsVDSCommand(<wbr>HostName = kvm-ldn-01,<br>
VdsIdVDSCommandParametersBase:<wbr>{runAsync=&#39;true&#39;,<br>
hostId=&#39;e050c27f-8709-404c-<wbr>b03e-59c0167a824b&#39;})&#39; execution failed:<br>
VDSGenericException: VDSNetworkException: Connection reset by peer<br>
2017-02-20 18:41:54,256Z ERROR<br>
[org.ovirt.engine.core.<wbr>vdsbroker.vdsbroker.<wbr>GetCapabilitiesVDSCommand]<br>
(DefaultQuartzScheduler7) [f8aa18b3-97b9-48e2-a681-<wbr>cf3aaed330a5]<br>
Command &#39;GetCapabilitiesVDSCommand(<wbr>HostName = kvm-ldn-01,<br>
VdsIdAndVdsVDSCommandParameter<wbr>sBase:{runAsync=&#39;true&#39;,<br>
hostId=&#39;e050c27f-8709-404c-<wbr>b03e-59c0167a824b&#39;,<br>
vds=&#39;Host[kvm-ldn-01,e050c27f-<wbr>8709-404c-b03e-59c0167a824b]&#39;}<wbr>)&#39;<br>
execution failed: java.net.ConnectException: Connection refused<br>
<br>
from the vdsm.log on the host:<br>
<br>
<br>
Feb 20 18:44:20 kvm-ldn-01 vdsm[42308]: vdsm vds.dispatcher ERROR SSL<br>
error receiving from &lt;yajsonrpc.betterAsyncore.<wbr>Dispatcher connected<br>
(&#39;::ffff:172.16.75.16&#39;, 38350, 0, 0) at 0x33b9bd8&gt;: unexpected eof<br>
Feb 20 18:44:24 kvm-ldn-01 vdsm[42308]: vdsm jsonrpc.JsonRpcServer<br>
ERROR Internal server error<br>
                                        Traceback (most recent call last):<br>
                                          File<br>
&quot;/usr/lib/python2.7/site-<wbr>packages/yajsonrpc/__init__.<wbr>py&quot;, line 547, in<br>
_handle_request...<br>
<br>
Any ideas what might be going on here?<br>
<br>
Thanks,<br>
<br>
Cam<br>
<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></div>