Hi Steffen,<br><br>There are two reasons I can think of that can cause that behaviour:<br><br>1) The next monitoring cycle hasn't been triggered.<br>2) The monitorization was triggered, but the command crashed and it didn't return neither FAILURE or SUCCESS to the core.<br>
<br>I've made a couple of tests and found that, indeed, there is a bug :/<br>You can its ticket here [1].<br><br>The problem is that the core sends the monitoring request to the ssh driver, and it is supposed to return FAILURE or SUCCESS. Instead, the driver is crashing, and the Host and VM keep the last monitoring data (and status).<br>
<br>This could also cause trouble if the motorization probe gets stuck, and doesn't end its execution.<br>We are aware of this problem, and we intend to add timeouts and checks to the drivers to ensure that the actions are always answered to the core.<br>
<br>Thanks for the feedback!<br>Carlos.<br><br>[1] <a href="http://dev.opennebula.org/issues/630">http://dev.opennebula.org/issues/630</a><br><br clear="all"><span style="border-collapse:collapse;color:rgb(136, 136, 136);font-family:arial, sans-serif;font-size:13px">--<br>
Carlos Martín, MSc<br>Project Major Contributor<br><span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34);background-repeat:initial initial">OpenNebula</span> - The Open Source Toolkit for Cloud Computing<br>
<a href="http://www.opennebula.org/" style="color:rgb(42, 93, 176)" target="_blank">www.<span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34);background-repeat:initial initial">OpenNebula</span>.org</a> | <a href="mailto:cmartin@opennebula.org" style="color:rgb(42, 93, 176)" target="_blank">cmartin@<span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34);background-repeat:initial initial">opennebula</span>.org</a></span><br>
<br><br><div class="gmail_quote">On Wed, May 11, 2011 at 5:10 PM, Steffen Neumann <span dir="ltr"><<a href="mailto:sneumann@ipb-halle.de" target="_blank">sneumann@ipb-halle.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I shut down some hosts (had to, there were NFS issues)<br>
and didn't delete the VMs beforehand.<br>
<br>
I am a bit surprised that onehost list still shows<br>
the node as "on":<br>
node02 default 2 1600 1280 1200 63G 58.1G on<br>
<br>
and that onevm list also reports the VMs as running:<br>
386 oneadmin suse113 runn 22 8G node02 08 06:51:45<br>
<br>
1) Why doesn't onehost report "err" if it can't execute<br>
the probes on the shutdown node ?<br>
<br>
2) Why doesn't onevm report "unknown" or whatever if it<br>
can't reach the not-running VM on the not-running node ?<br>
<br>
Should I open (one or two ?) tickets ?<br>
<br>
Yours,<br>
Steffen<br>
<br>
<br>
--<br>
IPB Halle AG Massenspektrometrie & Bioinformatik<br>
Dr. Steffen Neumann <a href="http://www.IPB-Halle.DE" target="_blank">http://www.IPB-Halle.DE</a><br>
Weinberg 3 <a href="http://msbi.bic-gh.de" target="_blank">http://msbi.bic-gh.de</a><br>
06120 Halle Tel. <a href="tel:%2B49%20%280%29%20345%205582%20-%201470" value="+4934555821470" target="_blank">+49 (0) 345 5582 - 1470</a><br>
<a href="tel:%2B49%20%280%29%20345%205582%20-%200" value="+4934555820" target="_blank">+49 (0) 345 5582 - 0</a><br>
sneumann(at)IPB-Halle.DE Fax. <a href="tel:%2B49%20%280%29%20345%205582%20-%201409" value="+4934555821409" target="_blank">+49 (0) 345 5582 - 1409</a><br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
</blockquote></div><br>