Re: Horrible clock drift help



Jeremy Parrish wrote:

Greetings,

We just bought 7 new servers from SuperMicro, and they all have the same
problem. They all gain about 1 second every 10 seconds or so (10% too
fast). I have tried various versions of Linux kernels (in particular,
2.4.27, 2.6.15, 2.6.15-smp, 2.6.16.20...) with all kinds of kernel
options (noapic, acpi=off, clock=tsc, the list goes on...). There is no
noticeable difference between any of those.

The servers use the Intel E7230 chipset and have Pentium D 805
processors. Ntpd does not seem to correct the clock at all (I've let it
run for more than a day). I've tried installing adjtimex, and it adjusts
the rate of the clock by about -3000 seconds per day, but I would
something more accurate.

Is there a way I can make ntpd play nice with such a horrible drift?

Thanks in advance,

Jeremy

_______________________________________________
questions mailing list
questions@xxxxxxxxxxxxxxxxx
https://lists.ntp.isc.org/mailman/listinfo/questions


Suggest you purchase hardware that works correctly!! Ntpd cannot correct a frequency error greater than 500 parts per million or about 43 seconds per day. Most computers have native clock frequency errors of less than 50 PPM.

Thank you for warning us about SuperMicro. I will make certain that I never buy their products!!!

.



Relevant Pages

  • Re: ntpq times out if NMEA refclock configured?
    ... I'm trying to add a GPS refclock to my server. ... clock, I'm now using a Garmin GPS25 and the NMEA refclock. ... Running minicom at 4800 Baud with NTPD stopped shows the GPS serial data ... The servers appear to have wildly differing opinions as to what time it is. ...
    (comp.protocols.time.ntp)
  • Re: timekeeping on jail servers
    ... Is there any special reason you do not want to use ntpdate from cron? ... Is working fine for me on FreeBSD jail servers. ... ntpd works by speeding up or slowing down the clock to catch up to the ... over time ntpd will tune the clock so ...
    (freebsd-questions)
  • Re: synchronization
    ... At the maximum slew rate of 500 parts per million, it will take several hours to bring your clock into synchronization. ... ntpd should set the clock unconditionally at startup; e.g. it should query the servers to find out what time it is and then set your clock to that time. ... Look for servers near you in geographical space and test them for nearness in net space (low round trip delays). ...
    (comp.protocols.time.ntp)
  • Re: keeping ntpd running
    ... threshold is used by the clustering algorithm as it casts off outlyer ... servers until the total remaining is not more than this value. ... been collected from each of at least four servers, the clock would be ... > This scenario is less likely using ntpd is the -g option is used as well. ...
    (comp.unix.solaris)
  • Re: ntpd -gq VS ntpdate -B
    ... Ntpd -qg with this time difference has the same behavior. ... See following reference of ntpdate manual: ... If ntpdate determines the clock is in error more than 0.5 second ... the servers you have chosen to use. ...
    (comp.protocols.time.ntp)