<html><body>
<div style="font-size: 13.3333px; font-family: Tahoma; color: rgb(0, 0, 0); font-weight: 400; font-style: normal; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(0, 0, 0, 0);">Here are the logs as requested.</div>
<div style="font-size: 13.3333px; font-family: Tahoma; color: rgb(0, 0, 0); font-weight: 400; font-style: normal; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(0, 0, 0, 0);"> </div>
<div style="font-size: 13.3333px; font-family: Tahoma; color: rgb(0, 0, 0); font-weight: 400; font-style: normal; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(0, 0, 0, 0);"> </div>
<div id="signature" style="font-family: Tahoma; color: rgb(0, 0, 0); font-size: 13.3333px; font-weight: 400; font-style: normal; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(0, 0, 0, 0);">
<div>
<div>
<div>Bryan Sockel<br />
Systems Administrator<br />
<a href="http://www.altn.com/" target="_blank">Alt-N Technologies</a> | Grapevine, TX<br />
Office 817.601.3222 x233<br />
<br />
Sent using Alt-N's own <a href="http://www.altn.com/" target="_blank">MDaemon Messaging Server</a><br />
Get to know the Alt-N family by liking us on <a href="https://www.facebook.com/pages/Alt-N-Technologies-MDaemon/220307374735000?ref=hl" target="_blank">Facebook</a>!</div>
</div>
<div> </div>
</div>
</div>
<div style="font-family: Tahoma; color: rgb(0, 0, 0); font-size: 13.3333px; font-weight: 400; font-style: normal; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(0, 0, 0, 0);">
<blockquote style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">-----Original Message-----<br />
From: "piotr.kliczewski@gmail.com -- Piotr Kliczewski" <piotr.kliczewski@gmail.com><br />
To: Bryan Sockel <Bryan.Sockel@altn.com><br />
Cc: "users@ovirt.org" <users@ovirt.org><br />
Date: Thu, 14 Sep 2017 21:30:19 +0200<br />
Subject: Re: [ovirt-users] Server Not Responding<br />
<div style="font-family: monospace, courier new, courier">Bryan,<br />
<br />
In your engine logs I see :<br />
<br />
2017-09-13 04:07:07,599-05 ERROR<br />
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]<br />
(DefaultQuartzScheduler3) [] Command 'GetAllVmStatsVDSCommand(HostName<br />
= vm-host-colo-1, VdsIdVDSCommandParametersBase:{runAsync='true',<br />
hostId='e75d4446-9bfc-47cb-8bf8-a2e681720b66'})' execution failed:<br />
VDSGenericzException: VDSNetworkException: Heartbeat exceeded<br />
<br />
It would br great to understand what happened on vdsm side because the<br />
engine was still trying to connect at: 2017-09-13 09:30:46,275-05<br />
<br />
In vdsm logs you provided I see that they start at 2017-09-13<br />
09:01:08,895-0500 and end at 2017-09-13 09:53:24,760-0500.<br />
<br />
Please provide vdsm logs from the time the issue occurred.<br />
<br />
Thanks,<br />
Piotr<br />
<br />
On Wed, Sep 13, 2017 at 5:09 PM, Bryan Sockel <<a href="mailto:Bryan.Sockel%40altn.com">Bryan.Sockel@altn.com</a>> wrote:<br />
><br />
> Hi<br />
><br />
> Having an issue where i frequently have a server that is set to not<br />
> responsive. VM's are set to unknown status, but still continue to run.<br />
> This issue is isolated to just a single host. My Setup is currently a 2<br />
> Data Center Configuration with 2 servers in each data center. Issue is<br />
> occurring at my remote site.<br />
><br />
> The primary storage volumes are setup on dedicated hardware, with the<br />
> arbiter running on the server that is having issues. There is also another<br />
> gluster replica volume hosted on this box, the replica is the other<br />
> dedicated server.<br />
><br />
> The logs are showing:<br />
><br />
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]<br />
> (DefaultQuartzScheduler8) [] Command 'GetCapabilitiesVDSCommand(HostName =<br />
> vm-host-colo-1, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',<br />
> hostId='e75d4446-9bfc-47cb-8bf8-a2e681720b66',<br />
> vds='Host[vm-host-colo-1,e75d4446-9bfc-47cb-8bf8-a2e681720b66]'})' execution<br />
> failed: java.rmi.ConnectException: Connection timeout<br />
><br />
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]<br />
> (DefaultQuartzScheduler8) [] Failure to refresh host 'vm-host-colo-1'<br />
> runtime info: java.rmi.ConnectException: Connection timeout.<br />
><br />
><br />
> I have attached the vdsm.log from the server with issues and the engine.log.<br />
><br />
> Thanks<br />
><br />
> Bryan Sockel<br />
><br />
><br />
> _______________________________________________<br />
> Users mailing list<br />
> <a href="mailto:Users%40ovirt.org">Users@ovirt.org</a><br />
> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br />
></div>
</blockquote>
</div>
</body></html>