[ntp:questions] Flash 400 on all peers; can't get ntpd to be happy
mlichvar at redhat.com
Tue Mar 8 09:16:56 UTC 2011
On Sun, Mar 06, 2011 at 11:22:34AM +0000, David Woolley wrote:
> Ralph wrote:
> >filtoffset= 67671.8 66534.8 65931.3 65118.0 63317.3 63029.5 62216.4 58156.6,
> Your frequency error is way outside any reasonable bounds, which is
> reflecting in a very high jitter, which is probably the ultimate
> cause of rejection.
> This system is not savable by NTP.
This seems to be a common problem and with virtual machines getting
everywhere it will probably only get worse. I'm wondering how hard it
would be for ntpd to detect that the clock frequency is outside the
acceptable range and write a "your clock is broken" message to syslog?
More information about the questions