Hi Gerry,
You are right, the default in 4.4 is 60 seconds.
Best regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
www.c12g.com | @C12G | es.linkedin.com/in/tinova
--
Confidentiality
Hi Gerry,
This is an error message, so it cannot be disabled. A lower monitoring
interval value would help, but the monitoring information won't be as
precise.
Regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure
Hi Tino,
Where can I set the monitoring interval?
Gerry
On 09/01/2014 09:53, Tino Vazquez wrote:
Hi Gerry,
This is an error message, so it cannot be disabled. A lower monitoring
interval value would help, but the monitoring information won't be as
precise.
Regards,
-Tino
--
Hi Gerry,
You can set it in /etc/one/oned.conf,
MONITORING_INTERVAL=10
The default is 10 seconds. You need to restart OpenNebula after making
the change.
Regards,
-Tino
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure
Hi Tino,
My default 4.4 oned.conf has the setting below.
Gerry
#MANAGER_TIMER = 30
MONITORING_INTERVAL = 60
MONITORING_THREADS = 50
#HOST_PER_INTERVAL = 15
#HOST_MONITORING_EXPIRATION_TIME = 43200
#VM_PER_INTERVAL = 5
#VM_MONITORING_EXPIRATION_TIME =
Hi,
Below are entries from /var/log/one/oned.log which report error:
error: columns vmid, last_poll are not unique. It looks like the
monitoring of VM 1638 and VM 1634. However, the SQL INSERT commands are
the same which causes the error. This also happens for host_moitoring.
It is
Hi,
This bug has been corrected on the development branch [1], so this
will be fixed in future releases.
Since the fix is done in the core, I am afraid you need to apply the
patch and recompile OpenNebula.
Regards,
-Tino
[1] http://dev.opennebula.org/issues/2544
--
OpenNebula - Flexible
Hi Tino,
Thanks for the update. I'd prefer not to recompile so I'll wait for
the next release.
In the meantime, is there any way to lessen the logging. Would
decreasing the frequency of monitoring help?
Regards,
Gerry
On 08/01/2014 14:10, Tino Vazquez wrote:
