[BBLISA] ntp question

Dave Pascoe km3t at km3t.org
Tue Mar 17 17:22:36 EDT 2009


This is a decent way to deal with it.

You can also use check_ntpd in Nagios and restart ntpd as needed on
hosts that appear to become unsynchronized.  The penalty for a false
positive is small.

Also, ntpdate should really be run right before starting ntpd.  ntpdate
sets clocks that have become far off due to hardware clocks skew and
then ntpd keeps everything in fine sync.

I have also found ntpd stability highly variable on VMs.  Just running
ntpdate there via cron seems like the path of least resistance.  On some
VM environments the host system already keeps the VMs in sync (it runs
ntpd and auto-syncs the VM clocks).

-Dave


Rudie, Tony wrote:
> ntpd isn't perfect at dealing with VMs either.  My organization has a
> cron job to monitor ntpd and make sure the time is still accurate,
> and there's some sophisticated logic there to minimize false
> positives, but it still throws a couple of valid alerts every week,
> (always on VMs.  The job runs everywhere, but...) and restart ntpd.
> 
> 
> Actually, it's not a cron job.  The monitoring system runs the
> check-script, and throws the alert based on return code.
> 
> 
> - Tony Rudié




More information about the bblisa mailing list