nanog mailing list archives
Re: NTP Issues Today
From: Darius Jahandarie <djahandarie () gmail com>
Date: Tue, 20 Nov 2012 19:56:40 -0500
On Tue, Nov 20, 2012 at 7:49 PM, Jimmy Hess <mysidia () gmail com> wrote:
Are you sure that you are actually using NTP to set your clock? For you to sync with 2000, you should have had multiple confused peers from multiple time sources; possibly a false radio signal.... NTP by default has a panic threshold of 1000 seconds. This _should_ have caused NTP to execute a panic shutdown, instead of setting the clock back 30 million seconds.
For VMWare at least, their official recommendation[1] for NTP is to tinker panic 0 for suspend/resume reasons. I've seen it default in some places. [1] http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427 -- Darius Jahandarie
Current thread:
- Re: NTP Issues Today, (continued)
- Re: NTP Issues Today George Herbert (Nov 20)
- Re: NTP Issues Today Leo Bicknell (Nov 20)
- Re: NTP Issues Today Darius Jahandarie (Nov 20)
- Re: NTP Issues Today Mike Lyon (Nov 20)
- Re: NTP Issues Today Jared Mauch (Nov 20)
- Picking outside NTP servers (Re: NTP Issues Today) Jay Ashworth (Nov 20)
- Re: Picking outside NTP servers (Re: NTP Issues Today) George Herbert (Nov 20)
- Re: Picking outside NTP servers (Re: NTP Issues Today) Majdi S. Abbas (Nov 20)
- Re: NTP Issues Today Ask Bjørn Hansen (Nov 21)
- Re: NTP Issues Today Darius Jahandarie (Nov 20)
- Re: NTP Issues Today Blake Dunlap (Nov 20)
- Re: NTP Issues Today George Herbert (Nov 20)
- Re: NTP Issues Today Robert E. Seastrom (Nov 21)
- Re: NTP Issues Today Greg Ihnen (Nov 21)
- Re: NTP Issues Today Clay Haynes (Nov 19)