<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif"><span style="font-family:arial">On Mon, Feb 3, 2014 at 9:53 PM, Doron Fediuck </span><span dir="ltr" style="font-family:arial"><<a href="mailto:dfediuck@redhat.com" target="_blank">dfediuck@redhat.com</a>></span><span style="font-family:arial"> wrote:</span><br>
</div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">
<div class="h5"><br>
<br>
----- Original Message -----<br>
> From: "Andrew Lau" <<a href="mailto:andrew@andrewklau.com">andrew@andrewklau.com</a>><br>
> To: "users" <<a href="mailto:users@ovirt.org">users@ovirt.org</a>><br>
> Sent: Monday, February 3, 2014 12:32:45 PM<br>
> Subject: [Users] Hosted Engine always reports "unknown stale-data"<br>
><br>
> Hi,<br>
><br>
> I was wondering if anyone has this same notice when they run:<br>
> hosted-engine --vm-status<br>
><br>
> The "engine status" will always be "unknown stale-data" even when the VM is<br>
> powered on and the engine is online. engine-health will actually report the<br>
> correct status.<br>
><br>
> eg.<br>
><br>
> --== Host 1 status ==--<br>
><br>
> Status up-to-date : False<br>
> Hostname : 172.16.0.11<br>
> Host ID : 1<br>
> Engine status : unknown stale-data<br>
><br>
> Is it some sort of blocked port causing this or is this by design?<br>
><br>
> Thanks,<br>
> Andrew<br>
><br>
</div></div>> _______________________________________________<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" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
<br>
Hi Andrew,<br>
it looks like an issue with the time stamp.<br>
Which time stamp do you have? How relevant is it?<br>
</blockquote></div><br></div><div class="gmail_extra"><div class="gmail_default" style="font-family:tahoma,sans-serif">timestamps seem to be outdated by a lot, interesting error in the broker.log</div><div class="gmail_default" style="font-family:tahoma,sans-serif">
<br></div><div class="gmail_default"><div class="gmail_default"><font face="tahoma, sans-serif">Thread-24::INFO::2014-02-03 22:33:14,801::engine_health::90::engine_health.CpuLoadNoEngine::(action) VM not running on this host, status down</font></div>
<div class="gmail_default"><font face="tahoma, sans-serif">Thread-22::INFO::2014-02-03 22:33:14,834::mem_free::53::mem_free.MemFree::(action) memFree: 27382</font></div><div class="gmail_default"><font face="tahoma, sans-serif">Thread-23::ERROR::2014-02-03 22:33:14,922::cpu_load_no_engine::156::cpu_load_no_engine.EngineHealth::(update_stat_file) Failed to getVmStats: 'pid'</font></div>
<div class="gmail_default"><font face="tahoma, sans-serif">Thread-23::INFO::2014-02-03 22:33:14,923::cpu_load_no_engine::121::cpu_load_no_engine.EngineHealth::(calculate_load) System load total=0.0124, engine=0.0000, non-engine=0.0124</font></div>
<div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">I'm assuming that update_stat_file is the metadata file the vm-status is getting pulled from?</div></div></div></div>