On 9/24/2013 4:53 AM, danta wrote:
We have some problems using collectd and ntpd.
Whenever ntpd sets the clock in the past (because of a clock drift),
collectd sleeps until it is back at it's 'normal' time.
To give an example:
- Suppose it's 10:00am,
- ntpd sees a large clock drift and set the clock to 09:45am
- collectd will sleep till 10:00am
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization/chap-Virtualization-KVM_guest_timing_management.html
http://kb.vmware.com/kb/1006427
How big is the time step? You may want to look at the -g and -x options
that are being passed to the ntpd daemon. Under RHEL, these are set in
/etc/sysconfig/ntpd.
http://www.eecis.udel.edu/~mills/ntp/html/ntpd.html
And make sure that there is no periodic process running "ntpdate"
somewhere in the background. You may want to check through the logfiles
to figure out whether it is ntpd that is stepping the clock or some
other process.
_______________________________________________
collectd mailing list
collectd@verplant.org
http://mailman.verplant.org/listinfo/collectd
