[ntp:questions] Odd (mis)behavior when reference clock fails

Kevin Oberman oberman at es.net
Tue Sep 16 16:29:54 UTC 2008

We have a fairly large "mesh" of NTP servers spread across the
US. Almost all have PPS reference clocks and are quite
accurate. Recently one of the reference clocks located across the county
seems to have failed. Such is life.

The problem is that the system's time started drifting and eventually
became far enough out of sync with the mesh to be marked as a bad

The only way I could get the clock to slew or step the time was to edit
the configuration and comment out the reference clock and PPS. It looks
like the system will only use the time from a reference clock when and if
the clock is configured, even if it can't be read.

Is there any way to "fix" this?
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 224 bytes
Desc: not available
URL: <http://lists.ntp.org/pipermail/questions/attachments/20080916/b888aa34/attachment.pgp>

More information about the questions mailing list