Ntpd Frequency Error Ppm Exceeds Tolerance 500 Ppm
gmail com> Cc: "freeipa-users redhat com" Subject: Re: [Freeipa-users] ntpd frequency error xxx PPM exceeds tolerance 500 PPM Date: Fri, 11 Sep 2015 13:40:03 -0700 Has this got anything to do with ipa ? The messages frequency error ppm exceeds tolerance 500 ppm solaris started only recently, which makes me think that it's not a hardware issue. There were
Ntp Ppm
only two notable changes to this system recently. The hdd had to be replaced, and a replica was set up. Could either have frequency error wiki any part to play ? On Thu, Sep 10, 2015 at 6:03 AM, Prasun Gera wrote:The hardware is not very old (ivybridge). The entries appear every few minutes in the log. The /etc/ntp.conf has ntp drift tolerance not been modified manually. It lists 3 servers - 0.rhel.pool.ntp.org, 1 and 2. At the end, 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
Ntp Tolerance
to ~50 ms. The ping to local servers is under 1 ms. I followed steps from the first link (ntpd -qg), and the messages 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 wrote:If could be the server is trying to access the time server over a heavily congested network which could cause these types of problems.How old is the hardware?How often to these entries appear in the log?What is the ping / traceroute to
gera gmail com> Cc: "freeipa-users redhat com" Subject: Re: [Freeipa-users] ntpd frequency error xxx PPM exceeds tolerance 500 PPM Date: Thu, 10 Sep 2015 14:27:21 +0200 If could be the server is trying to frequency error ppm exceeds tolerance 500 ppm linux access the time server over a heavily congested network which could cause these types tinker panic 0 of problems.How old is the hardware?How often to these entries appear in the log?What is the ping / traceroute to the time
Ntp Drift File
server you are using?Are there any other machines on the same local network that are using this timeserver? Do they have problems?On 10 September 2015 at 14:18, Prasun Gera wrote:So I did https://www.redhat.com/archives/freeipa-users/2015-September/msg00157.html a bit of googling and tinker panic 0 only makes sense for virtual machines. Is there any way to confirm if it is indeed a hardware issue ? On Thu, Sep 10, 2015 at 5:16 AM, Andrew Holway wrote:Thats odd. You would normally not need it on bare metal. It could be broken hardware.On 10 September 2015 at 14:05, Prasun Gera wrote:Thanks. I'm not virtualizing https://www.redhat.com/archives/freeipa-users/2015-September/msg00152.html though. Should I still add it ? On Thu, Sep 10, 2015 at 5:02 AM, Andrew Holway wrote:Hi,I assume you are virtualising.Try adding "tinker panic 0" to /etc/ntp.conf. It should make it tolerant to heavily drifting virtual clocks.Cheers,Andrew On 10 September 2015 at 13:46, Prasun Gera wrote:OS: RHEL 7.1 w IDMI'm seeing these messages in my master's log messages. I don't know if it's related, but I think I started seeing them after I set up a replica. Everything seems to be working fine, but I'm worried that things will break if delta grows beyond a point. I tried steps in https://access.redhat.com/solutions/35640, but it didn't really help. The messages still appear regularly in the log. -- Manage your subscription for the Freeipa-users mailing list: https://www.redhat.com/mailman/listinfo/freeipa-users Go to http://freeipa.org for more info on the project Follow-Ups: Re: [Freeipa-users] ntpd frequency error xxx PPM exceeds tolerance 500 PPM From: Prasun Gera References: [Freeipa-users] ntpd frequency error xxx PPM exceeds tolerance 500 PPM From: Prasun Gera Re: [Freeipa-users] ntpd frequency error xxx PPM exceeds tolerance 500 PPM From: Andrew Holway Re: [Freeipa-users] ntpd frequency error xxx PPM exceeds tolerance 500 PPM From: Prasun Gera Re: [Freeipa-users] ntpd frequency error xxx PPM exceeds tolerance 500 PPM From: Andrew Holway Re: [Freeipa-users] ntpd fr
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of http://serverfault.com/questions/378784/ntpd-frequency-error-1732-ppm-exceeds-tolerance-500-ppm this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody frequency error can answer The best answers are voted up and rise to the top ntpd frequency error -1732 PPM exceeds tolerance 500 PPM up vote 1 down vote favorite I'm getting this error on my PC: frequency error -1732 PPM exceeds tolerance 500 PPM Any ideas? windows ntpd share|improve this question asked Apr 12 '12 at 8:44 user626528 154127 add a comment| 2 Answers 2 frequency error ppm active oldest votes up vote 6 down vote accepted This means that the difference between your local time and the server you're syncing with has exceed ntpd's limit. ntpd will only sync the local time if it is relatively close to the time server. This is why Red Hat (as an example) uses ntpdate the first time you start the ntpd service to set the local time to be in the right ball park. You should also make sure that the ntp servers you are syncing with are relatively close. You can do these steps manually if you want (e.g. you're not running Red Hat which includes the ntpdate step in it's restart script): # /etc/init.d/ntpd stop # ntpdate # /etc/init.d/ntpd start However, if you're seeing these errors in a log file for a machine that has been up sometime and it is a virtual machine then there may be a different issue at play. Virtual Machines have problems with their time because there isn't a proper hardware timing signal coming in. Follow VMWare's advice found here (it is equally relevant for other virtualisation platforms): http://kb.vmware.com/selfservice/m