[ntp:questions] Synchronisation problems updating to version 4.2.0a on multiple platforms.

Jacobo.Matute at esa.int Jacobo.Matute at esa.int
Fri Feb 11 13:11:25 UTC 2005


Hi,

We have been using without any problem the ntp 4.1.1 in most of our linux
systems (and in some of our solaris and windows systems) to synchronize with
two ACOLA NTP servers, that are fed by two GPS Clocks.

We wanted to upgrade to version 4.2.0a on those systems but we are
experiencing the same problem on all the platforms.
After ntp boots and the initialisation is done, the client selects a primary
a secondary ntp server to synchronize. Soon after first synchronisation, the
ntp servers are marked as falseticker with the status code x1xx, not passing
the correctness tests ( no intersection interval between the servers).

Also, sometimes, at first sight randomly, the client reselects an ntp server
and synchronize with it, losing the synchronisation soon after that.

Has somebody experience this problem with the new version? Which would be the
best way to trace the problem?

Any help would be much appreciated....

Many thanks!,

Jacobo Matute

I attach some info that might help....
--------------------------------------------------------

We don't use any specific configuration on the ntp.conf file:



This is the typical ntpq output on a linux box (SLES 9)

 # ntpq -p
   remote           refid      st t when poll reach   delay   offset  jitter


==============================================================================

 xdgpsas1          .GPS.        1 u   24   64  377    2.017  134.355   1.738
 xdgpsbs1          .GPS.        1 u    2   64  377    2.237  156.553   0.976

 # ntpq -c as

ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1  5140  9154   yes   yes  none falsetick   reachable  5
  2  5141  9154   yes   yes  none falsetick   reachable  5

This is the typical ntpq output on a Windows box (XP)

 # ntpq -p
     remote           refid      st t when poll reach   delay   offset
jitter
==============================================================================
xdgpsas1          .GPS.          1 u   20   64  377    2.040  129.165   1.001
xdgpsbs1          .GPS.          1 u   52   64  377    2.040  150.160   0.428


 # ntpq -c as

ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1 65356  b134   yes   yes  none falsetick   reachable  3
  2 65357  b134   yes   yes  none falsetick   reachable  3


Peerstats example since ntp client is booted (192.168.0.1/2 are the NTP
servers):

53396 33450.227 192.168.0.1 9014 -0.001867879 0.002959000 7.939453624
0.000000954
53396 33451.225 192.168.0.2 9014 0.019179286 0.002411000 7.939453620
0.000000954
53396 33468.603 192.168.0.1 9014 -0.001491993 0.003006000 7.939453624
0.000000954
53396 33469.604 192.168.0.2 9014 0.017000810 0.003608000 7.939453629
0.000000954
53396 33532.684 192.168.0.1 9014 -0.028867393 0.002390000 3.940670432
0.027375400
53396 33532.684 192.168.0.2 9014 -0.010634767 0.002578000 3.940666686
0.027635577
53396 33596.737 192.168.0.1 9014 -0.028614961 0.002210000 1.941398834
0.019179665
53396 33596.739 192.168.0.2 9014 -0.010634767 0.002578000 1.941875094
0.019615795
53396 33661.793 192.168.0.1 9614 -0.028614961 0.002210000 0.942073348
0.015662547
53396 33662.793 192.168.0.2 9414 -0.008437648 0.002379000 0.942074292
0.014742117
53396 33724.822 192.168.0.1 9614 -0.028614961 0.002210000 0.442961387
0.018278283
53396 33727.824 192.168.0.2 9414 0.015772051 0.002150000 0.442197795
0.021566939
53396 33790.866 192.168.0.1 9614 -0.028614961 0.002210000 0.193875094
0.022971137
53396 33790.866 192.168.0.2 9414 0.015772051 0.002150000 0.192978376
0.020217399
53396 33855.912 192.168.0.2 9414 0.015772051 0.002150000 0.068152689
0.020532399
53396 33855.913 192.168.0.1 9614 -0.028614961 0.002210000 0.069789330
0.028308532
53396 33920.962 192.168.0.1 9614 -0.028614961 0.002210000 0.008245491
0.033083819
53396 33921.962 192.168.0.2 9414 0.015772051 0.002150000 0.006122346
0.021958046
53396 33984.010 192.168.0.1 9614 -0.028614961 0.002210000 0.009156624
0.038584988
53396 33986.010 192.168.0.2 9414 0.015772051 0.002150000 0.006677697
0.025709994
53396 34049.059 192.168.0.1 9114 -0.028614961 0.002210000 0.008434690
0.045831444
53396 34050.059 192.168.0.2 9614 0.015772051 0.002150000 0.007512775
0.028361183
53396 34115.112 192.168.0.1 9114 0.038673528 0.002033000 0.005535821
0.033720273
53396 34116.115 192.168.0.2 9614 0.015772051 0.002150000 0.008468498
0.031324385
53396 34180.167 192.168.0.1 9114 0.038673528 0.002033000 0.006200803
0.022362408
53396 34180.167 192.168.0.2 9614 0.015772051 0.002150000 0.009262209
0.034526491
53396 34243.220 192.168.0.1 9414 0.038673528 0.002033000 0.005930392
0.015463946
53396 34244.222 192.168.0.2 9614 0.037812024 0.002284000 0.008680023
0.017537648
53396 34307.276 192.168.0.1 9414 0.038673528 0.002033000 0.006614298
0.010038961
53396 34308.276 192.168.0.2 9114 0.060769008 0.002268000 0.006718538
0.011292031
53396 34370.328 192.168.0.1 9114 0.038673528 0.002033000 0.007073732
0.006399636
53396 34373.331 192.168.0.2 9114 0.060769008 0.002268000 0.007081058
0.007241824
53396 34433.380 192.168.0.1 9114 0.038673528 0.002033000 0.007835978
0.004204811
53396 34438.384 192.168.0.2 9114 0.060769008 0.002268000 0.007448500
0.004220591
53396 34499.433 192.168.0.1 9114 0.038673528 0.002033000 0.008709024
0.003985174
53396 34503.438 192.168.0.2 9114 0.060769008 0.002268000 0.007512660
0.003174546
53396 34565.487 192.168.0.1 9114 0.038673528 0.002033000 0.008882345
0.005863802

After that we get some re-synchronisation from time to time.





More information about the questions mailing list