# Monitoring hosts

**URL:** <https://forum.opennebula.io/t/monitoring-hosts/3692>\
**Category:** Product Support\
**Created:** [January 31, 2017, 5:40pm UTC](https://forum.opennebula.io/t/monitoring-hosts/3692 "2017-01-31T17:40:35Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![GabrielDias](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/gabrieldias/32/5457_2.png) [@GabrielDias](https://forum.opennebula.io/u/GabrielDias)\
**Post date:** [January 31, 2017, 5:40pm UTC](https://forum.opennebula.io/t/monitoring-hosts/3692/1 "2017-01-31T17:40:35Z")

</div>

Hi,

How I can set a minimum polling interval to monitoring hosts?

e.g.  
I have 3 servers with shared storage.

Host hook enabled:

```sh
HOST_HOOK = [
    NAME = "error",
    ON = "ERROR",
    COMMAND = "ft/host_error.rb",
    ARGUMENTS = "$ID -m -p 5",
    REMOTE = "no" ]

```

I restart one of the servers, but VMs doesn`t migrate, because HOST isn`t in ERROR status.  
But, I need minimal - 20 seconds to check HOST status.

I found this topic, but can`t understand how it can help me.

> [@Host failure handling interval](https://forum.opennebula.io/t/host-failure-handling-interval/321):
>
> Hello, I have setup with OpenNebula with this configuration: 3 hosts (one of this node running oned) with Ubuntu Server 14.04 LTS + KVM as hypervisor + openvswitch as network Storage is ceph. And I have some issues with host failure detection. My testing case is deploy vm to one of the host, after vm succesfully booted, I’m going to host, when it running, and just shutdown this host (by running poweroff command). after that host changing state from ok to updated, and after long time (30-40…

---

<div class="post-metadata">

**Author:** ![ruben](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/ruben/32/19_2.png) [@ruben](https://forum.opennebula.io/u/ruben)\
**Post date:** [February 2, 2017, 2:52pm UTC](https://forum.opennebula.io/t/monitoring-hosts/3692/2 "2017-02-02T14:52:41Z")

</div>

This is set in oned.conf:

[http://docs.opennebula.org/5.2/deployment/open\_cloud\_host\_setup/monitoring.html](http://docs.opennebula.org/5.2/deployment/open_cloud_host_setup/monitoring.html)

You are interested in the -i argument for the collectd:

-i: Time in seconds of the monitorization push cycle. This parameter must be smaller than MONITORING\_INTERVAL (see below), otherwise push monitorization will not be effective.

---

<div class="post-metadata">

**Author:** ![GabrielDias](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/gabrieldias/32/5457_2.png) [@GabrielDias](https://forum.opennebula.io/u/GabrielDias)\
**Post date:** [February 3, 2017, 12:25am UTC](https://forum.opennebula.io/t/monitoring-hosts/3692/3 "2017-02-03T00:25:55Z")

</div>

Thank you for your reply.

It`s work, but I have a new problem. I`m imitating the host problem (down interface), host in ERROR state, but HOST\_HOOK doesn`t execute migrate VMs to another host.

VMs are still running on ERROR host, doesn`t ping, but in RUNNING status.

 ![](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/1/1a56cf1157c46ebe9886059a3c9347e1c9c38015.png)  
 ![](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/9/9c6bbdb2e3ba437b0a5e966f8c23b7ce9b857af3.png)

crmsh migrate services to another host.  
 ![](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/9/92a8ad4698c7858b464e691e93842b1454a8020f.png)

---

<div class="post-metadata">

**Author:** ![GabrielDias](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/gabrieldias/32/5457_2.png) [@GabrielDias](https://forum.opennebula.io/u/GabrielDias)\
**Post date:** [February 5, 2017, 8:49am UTC](https://forum.opennebula.io/t/monitoring-hosts/3692/4 "2017-02-05T08:49:31Z")

</div>

Is there any idea?

---

<div class="post-metadata">

**Author:** ![UAnton](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/uanton/32/6309_2.png) [@UAnton](https://forum.opennebula.io/u/UAnton)\
**Post date:** [February 5, 2017, 4:26pm UTC](https://forum.opennebula.io/t/monitoring-hosts/3692/5 "2017-02-05T16:26:27Z")

</div>

> [@VM HA not working after update to 5.2](https://forum.opennebula.io/t/vm-ha-not-working-after-update-to-5-2/3179):
>
> Hi! Test VM HA on 5.0.2 - all works fine! After update to 5.2 - hook not work. VMs still in UNKNOWN state. Checked configs on nodes - all ok.

---

<div class="post-metadata">

**Author:** ![GabrielDias](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/gabrieldias/32/5457_2.png) [@GabrielDias](https://forum.opennebula.io/u/GabrielDias)\
**Post date:** [February 5, 2017, 8:28pm UTC](https://forum.opennebula.io/t/monitoring-hosts/3692/6 "2017-02-05T20:28:51Z")

</div>

Yes. Now it works.  
Big thanks.

Now i try to minimise downtime)