The hardware is not very old (ivybridge). The entries appear every few minutes in the log. The /etc/ntp.conf has 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 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.516 On Thu, Sep 10, 2015 at 5:27 AM, Andrew Holway <andrew.hol...@gmail.com> 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 the time 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 <prasun.g...@gmail.com> wrote: > >> So I did 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 <andrew.hol...@gmail.com> >> 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 <prasun.g...@gmail.com> >>> wrote: >>> >>>> Thanks. I'm not virtualizing though. Should I still add it ? >>>> >>>> On Thu, Sep 10, 2015 at 5:02 AM, Andrew Holway <andrew.hol...@gmail.com >>>> > 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 <prasun.g...@gmail.com> >>>>> wrote: >>>>> >>>>>> OS: RHEL 7.1 w IDM >>>>>> >>>>>> I'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 >>>>>> >>>>> >>>>> >>>> >>> >> >
-- 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