[ntp:questions] ntp clients out of sync with server

naihong at gmail.com naihong at gmail.com
Wed Oct 29 00:37:19 UTC 2008


On Oct 28, 3:03 pm, Unruh <unruh-s... at physics.ubc.ca> wrote:
> "naih... at gmail.com" <naih... at gmail.com> writes:
> >I know 127.127.1.0 should appear in any clients'  configure file. But
>
> That should read "...should NEVER appear".
>
> >without this statement, the display from ntpq -p,  only display the
> >client out of sync with server. I mean tally '*' is missing from
>
> None.
>
> >server, I did not know which time the client  followed.  So add
> >127.127.1.0, just make sure the client sync to its own clock. At
> >beginning, I just follow  previous posts, use the simplest
> >configuration for orphan mode
>
> Why in the world would you want it to sync to its own clock?
> If it is not syncing to the server, THAT is the problem that needs to be
> solved, not some problem that there is no * in ntpq.
>
> What comes out of peerstats once you get rid of the local clock?
>
> >server's ntp.conf
> >driftfile "C:\Program Files\NTP\etc\ntp.drift"
> >tos orphan 10
> >client's ntp.conf
> >driftfile "C:\Program Files (x86)\NTP\etc\ntp.drift"
> >server 10.200.98.51 iburst
> >But this doesn't work. The clients cannot follow server's time after
> >about one day running.
>
> What kind of clients are they? If ntp finds the client is too far off the
> server, it gives up and does not try anymore.
>
> So, start up ntpd -g with the server, and then look at the peerstats file
> to see what is happening to the offset. Then look at the loopstats file as
> well.
> Also tell us which operating system you are using. And which version of
> ntpd
>
This is a LAN environment, all computers are in the same network
segment, same building.
Server is WinXP XP2, install Meinberg ntpd 4.2.4p5, disable w32time.
      service ntp start up with Meinberg's default setting:
      C:\Program Files\NTP\bin\ntpd.exe -U 3 -M -g -c "C:\Program Files
\NTP\etc\ntp.conf"

Client1, Vista x64, install Meinberg ntpd 4.2.4p5, disable w32time
Client2, WinXP XP3, install Meinberg ntpd 4.2.4p5, disable w32time
Client3, CentOS 5.2, install ntp-4.2.2p1

After get rid of local clock. One Client's  peerstats:
54768 46.406 10.200.98.51 9014 -0.038017114 0.000306409 7.937500956
0.000000954
54768 48.403 10.200.98.51 9014 -0.064618551 0.000291795 3.937508934
0.026601437
54768 50.403 10.200.98.51 9014 -0.064626478 0.000261123 1.937516673
0.018815662
54768 52.403 10.200.98.51 9014 -0.064552078 0.000416696 0.937522418
0.015320077
54768 54.402 10.200.98.51 9014 -0.064642234 0.000280164 0.437526228
0.013312644
54768 56.402 10.200.98.51 9014 -0.064641344 0.000289907 0.187528601
0.011906791
54768 58.403 10.200.98.51 9014 -0.064635652 0.000283088 0.062530022
0.010867030
54768 60.402 10.200.98.51 9014 -0.064647984 0.000275511 0.000030850
0.010065599
54768 62.402 10.200.98.51 9014 -0.064653534 0.000283184 0.000030850
0.000042888
54768 112.400 10.200.98.51 9014 -0.064749014 0.000277924 0.000388037
0.000124767
54768 178.397 10.200.98.51 9014 -0.064899955 0.000276278 0.000684287
0.000259442
54768 241.394 10.200.98.51 9014 -0.065027426 0.000298725 0.000808213
0.000344021
54768 304.391 10.200.98.51 9014 -0.065179532 0.000273336 0.000868389
0.000452187
54768 367.388 10.200.98.51 9014 -0.065336764 0.000279747 0.000896690
0.000546344
54768 430.385 10.200.98.51 9014 -0.065420572 0.000364421 0.000909053
0.000551227
54768 494.382 10.200.98.51 9014 -0.065626320 0.000265256 0.000920889
0.000646756
54768 560.379 10.200.98.51 9014 -0.065780028 0.000268319 0.000939873
0.000666959
54768 624.376 10.200.98.51 9014 -0.065921984 0.000273026 0.000934014
0.000665204
54768 690.373 10.200.98.51 9014 -0.066101032 0.000270696 0.000946025
0.000697892
54768 754.370 10.200.98.51 9014 -0.066225812 0.000286257 0.000937061
0.000676072
54768 817.367 10.200.98.51 9014 -0.066385850 0.000256096 0.000925107
0.000686414
54768 881.364 10.200.98.51 9014 -0.066542658 0.000294116 0.000926572
0.000695455
54768 945.361 10.200.98.51 9014 -0.066627817 0.000417715 0.000927277
0.000623911
54768 1011.358 10.200.98.51 9014 -0.066574980 0.000863147 0.000942515
0.000454266
54768 1075.355 10.200.98.51 9014 -0.067014922 0.000308414 0.000935247
0.000718587
54768 1140.352 10.200.98.51 9014 -0.066858390 0.000940082 0.000939059
0.000455869
54768 1206.349 10.200.98.51 9014 -0.067061963 0.000876897 0.000948435
0.000520336
54768 1270.346 10.200.98.51 9014 -0.067222507 0.000911194 0.000938182
0.000552473
54768 1335.344 10.200.98.51 9614 -0.067671481 0.000916143 0.000940468
0.000864462
54768 1399.336 10.200.98.51 9614 -0.067014922 0.000308414 0.005095755
0.001572922
54768 1463.329 10.200.98.51 9614 -0.067014922 0.000308414 0.005307104
0.003247092
54768 1529.322 10.200.98.51 9614 -0.056247920 0.000292353 0.002648235
0.009650302
54768 1595.315 10.200.98.51 9614 -0.052894009 0.000286015 0.001436868
0.011804385
54768 1658.309 10.200.98.51 9614 -0.052894009 0.000286015 0.001643527
0.010620305
54768 1723.304 10.200.98.51 9614 -0.052894009 0.000286015 0.002069093
0.009442148

its loopstats output:
54768 1335.343 -0.067671481 -46.699 0.023925482 0.000000 6
54768 1529.322 -0.056247920 -46.914 0.022741752 0.075862 6
54768 1595.315 -0.052894009 -47.115 0.021305985 0.100622 6


> >On Oct 28, 12:33=A0pm, Steve Kostecke <koste... at ntp.org> wrote:
> >> On 2008-10-28, naih... at gmail.com <naih... at gmail.com> wrote:
>
> >> > ... time island ...
>
> >> [snip]
>
> >> > I select the orphan mode. After the server and clients start up. At
> >> > first, the clents can sync to server's clock. But after 1 day, all 3
> >> > clients begin to sync to its local clock, not the server.
>
> >> > The output of ntpq -p is,
>
> >> > remote =A0 =A0 =A0 =A0refid =A0 =A0st t when poll reach delay offset ji=
> >tter
> >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=
> >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> > 10.200.98.51 =A0 =A0 =A0 127.0.0.1 5 u =A0105 =A0256 =A0377 =A00.299 -1=
> >.886 =A00.591
> >> > *LOCAL(0) =A0 =A0 .LOCL. =A0 12 l =A0 23 =A0 64 =A0377 =A00.000 =A00.00=
> >0 =A00.001
>
> >> > The ntp.conf on server is,
> >> > driftfile "C:\Program Files\NTP\etc\ntp.drift"
> >> > tos orphan 5
>
> >> > The ntp.conf on all 3 clients is(except the drift file location),
>
> >> > driftfile "C:\Program Files (x86)\NTP\etc\ntp.drift"
> >> > server 10.200.98.51 iburst
> >> > server 127.127.1.0
> >> > fudge 127.127.1.0 stratum 12
>
> >> The "clients" should not be using the Undisciplined Local Clock.
>
> >> > logconfig =3D all
> >> > logfile "C:\Program Files (x86)\NTP\etc\ntp.log"
> >> > statsdir "C:\Program Files (x86)\NTP\etc\log\"
> >> > statistics loopstats peerstats clockstats
> >> > filegen loopstats file loopstats type day enable
> >> > filegen peerstats file peerstats type day enable
> >> > filegen clockstats file clockstats type day enable
>
> >> > At beginning, the configuration file on client has only first 2 lines,
> >> > the lines from server 127.127.1.0 were added for debugging purpose.
>
> >> That is a misuse of the Undisciplined Local Clock.
>
> >> > The same thing happened two years ago, on different computer hardware.
> >> > At that time,I select undiscipline clock on server, and want 5 clients
> >> > sync to server. But after days running, the clients out of sync with
> >> > server, chasing their own clock. So I have to disable ntpd, and add
> >> > ntpdate to crond to sync the time by force.
>
> >> > Could any one give me some clues on this issue.
>
> >> Don't use the Undisciplined Local Clock on any ntpd which does not serve
> >> time to others.
>
> >> --
> >> Steve Kostecke <koste... at ntp.org>
> >> NTP Public Services Project -http://support.ntp.org/




More information about the questions mailing list