Ntp Frequency Error 511 Ppm Exceeds Tolerance 500 Ppm
Contents |
gmail com> Cc: "freeipa-users redhat com"
Ntp Ppm
AM, Prasun Gera
Frequency Error Wiki
there are also a couple of additional local servers with the comment added by /sbin/dhclient-script. The replica on the same network with an identical ntp.conf file doesn't have these messages in the current log. However, if I go back to a week, I see similar messages there too. The ping to public ntp servers varies from to a few ms to ~50 ms. The ping to local servers is under 1 ms. I followed steps from the first link (ntpd -qg), and the messages ntp drift tolerance have stopped for now, but I suspect that they will reappear later. That's what happened last time I tried that solution. This is the output from ntpq -pn on the master: remote refid st t when poll reach delay offset jitter==============================================================================+38.229.71.1 204.123.2.5 2 u 39 64 377 44.300 -1311.8 7.668+64.6.144.6 128.252.19.1 2 u 25 64 377 38.184 -1327.6 12.615-129.250.35.251 200.98.196.212 2 u 30 64 377 14.649 -1318.8 7.079 127.127.1.0 .LOCL. 10 l - 64 0 0.000 0.000 0.000*localnetip1 localnetref1 2 u 55 64 377 0.349 -1316.0 8.264-localnetip2 localnetref2 3 u 64 64 377 0.459 -1309.6 10.516On Thu, Sep 10, 2015 at 5:27 AM, Andrew Holway
Re: time reset, syncronisation lost and Large PPM values Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] tor wrote: > Something bothers ntpd so it looses sync about every
Ntp Tolerance
half hour. > The messages from two versions of ntpd are given below. This frequency error ppm exceeds tolerance 500 ppm linux is your problem: > Oct 19 17:19:09 srv3 ntpd[19356]: frequency initialized 500.000 from > /var/lib/ntp/drift > Oct 20 15:37:13 srv3 ntpd[20655]: tinker panic 0 frequency initialized 500.000 PPM from > /var/lib/ntp/drift > Oct 20 15:54:28 srv3 ntpd[20655]: frequency error 502 PPM exceeds tolerance > 500 PPM > Oct 20 16:09:31 srv3 ntpd[20655]: frequency error 502 PPM exceeds tolerance > https://www.redhat.com/archives/freeipa-users/2015-September/msg00157.html 500 PPM > Oct 20 16:13:47 srv3 ntpd[20655]: frequency error 502 PPM exceeds tolerance > 500 PPM > Oct 20 16:14:51 srv3 ntpd[20655]: frequency error 502 PPM exceeds tolerance > 500 PPM > Oct 20 16:15:57 srv3 ntpd[20655]: frequency error 502 PPM exceeds tolerance > 500 PPM > Oct 20 16:17:01 srv3 ntpd[20655]: frequency error 502 PPM exceeds tolerance > 500 PPM > Oct 20 16:18:06 srv3 ntpd[20655]: frequency error 502 http://lists.ntp.org/pipermail/questions/2005-October/007418.html PPM exceeds tolerance > 500 PPM You have acquired and institutionalized an absurd frequency correction (drift rate). This may have happened because the time was not set before starting ntpd, because the server stepped after ntpd was started, because you are running ntpd with the "-x" option, because ntpd was shut down or the system rebooted while ntpd was in the middle of slew correction, or a combination of these. You need to check your configuration and re-initialize things. 1) Make sure you are NOT using "-x" in the ntpd command line 2) In /etc/step-tickers, enter a list of reliable NTP servers that are likely to be up at the time your system boots 3) Make sure that all of the servers in /etc/ntp.conf are good and reporting similar times 4) # service ntpd stop 5) # rm /var/lib/ntp/drift 6) # service ntpd start 7) Wait for a day or 2 for things to stabilize without shutting down ntpd or rebooting the system -Tom Previous message: [ntp:questions] time reset, syncronisation lost and Large PPM values Next message: [ntp:questions] Re: time reset, syncronisation lost and Large PPM values Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the questions mailing list
error 512 PPM exceeds tolerance 500 PPM Should I be worried, or should I just configure logcheck to ignore them? I can't seem to http://forum.bytemark.co.uk/t/ntpd-27500-frequency-error-512-ppm-exceeds-tolerance-500-ppm/232 find any good information about this error, except that is has something to do with the hardware clock being too far behind the ntp clock, which is probably related to this problem: http://forum.bytemark.co.uk/viewtopic.php?id=569 jmitchell 2006-02-11 09:11:13 UTC #2 Has this been fixed? My logs are still full of this, and judging by ntpq -p my local clock really is drifting all frequency error over the place. My ntp.conf uses 0.uk.pool.ntp.org, 1.uk.pool.ntp.org, 2.uk.pool.ntp.org. Does anyone have any tips or pointers to getting this fixed? Thanks corford 2006-02-20 18:32:37 UTC #3 Just as a "me too" - I am also experiencing this problem (see snip from my logs below) 20 Feb 13:24:29 ntpd[19546]: frequency error -512 PPM exceeds tolerance 500 PPM20 Feb 13:28:50 ntpd[19546]: synchronized to ppm exceeds tolerance 130.159.196.118, stratum 220 Feb 13:28:50 ntpd[19546]: frequency error -512 PPM exceeds tolerance 500 PPM20 Feb 13:33:06 ntpd[19546]: synchronized to 158.43.128.33, stratum 220 Feb 13:35:18 ntpd[19546]: frequency error -512 PPM exceeds tolerance 500 PPM20 Feb 13:36:22 ntpd[19546]: synchronized to 130.88.200.6, stratum 220 Feb 13:43:44 ntpd[19546]: frequency error -512 PPM exceeds tolerance 500 PPM20 Feb 14:03:11 ntpd[19546]: synchronized to 158.43.128.33, stratum 220 Feb 14:03:11 ntpd[19546]: time reset -0.219111 s20 Feb 14:03:11 ntpd[19546]: frequency error -512 PPM exceeds tolerance 500 PPM20 Feb 14:07:29 ntpd[19546]: synchronized to 130.88.203.64, stratum 220 Feb 14:07:29 ntpd[19546]: frequency error -512 PPM exceeds tolerance 500 PPM20 Feb 14:13:55 ntpd[19546]: frequency error -512 PPM exceeds tolerance 500 PPM20 Feb 14:18:14 ntpd[19546]: frequency error -512 PPM exceeds tolerance 500 PPM20 Feb 14:34:19 ntpd[19546]: time reset -0.175730 s rvanrees 2006-03-22 09:43:19 UTC #4 Mattias Wikstrom: I'm getting a lot of these errors in my logs on two different VM's running on different hosts: ntpd[27500]: frequency error 512 PPM exceeds tolerance 500 PPM Should I be worried, or should I just configure logcheck to ignore them? I can't seem to find any good information