[ntp:questions] ntpd: more than 60 s behind

unruh unruh at wormhole.physics.ubc.ca
Wed Apr 20 15:11:15 UTC 2011


On 2011-04-20, asklucas <asklucas at gmx.net> wrote:
>
> Hello all!
>
> I installed Meinberg's build of ntpd for Windows:
> ntpd 4.2.4p8 at lennon-o Dec 09 10:46:55 (UTC+01:00) 2009  (3)
>
> While it initially synchronized successfully, it didn't work for two days. Now I'm more than 60 seconds behind.
>
> Connection to the closest remote NTP server works fine, see output of ntpdate below.
>
> What's wrong? I have no clue to begin troubleshooting...

What is wrong is that you have that stupid LOCAL in there. Do not do it.
never ever. (well, that is a bit strong, you can do it if you really
really know what you are doing and if you run a huge farm of machines
all getting theiry time from your machine)


>
> Thank you for your help!
>
> L.
>
>==============================================================================
>
> D:\util\system\NTP\bin>ntpdate -q 217.19.37.26
> server 217.19.37.26, stratum 1, offset 63.223438, delay 0.04553
> 20 Apr 08:42:32 ntpdate[4168]: step time server 217.19.37.26 offset 63.223438 sec
>
> D:\util\system\NTP\bin>ntpq -p
>      remote           refid      st t when poll reach   delay   offset  jitter
>==============================================================================
> *LOCAL(0)        .LOCL.          12 l   18   64  377    0.000    0.000   0.001

You system is using itself as the time source. Why? I have no idea. But
it is no wonder it is not doing a good job of feeding itself time. 

>  217.19.37.26    .ATOM.           1 u  781 1024  377   21.873  56147.1 3375.72
>  ptbtime1.ptb.de .PTB.            1 u  747 1024  377   43.859  52929.2 3343.98
>  217.19.37.27    .ATOM.           1 u  764 1024  377   21.023  52838.6 3394.36
>  ptbtime2.ptb.de .PTB.            1 u  768 1024  377   43.901  56232.9 3394.40
>  nav.metrologie. .ATOM.           1 u  749 1024  377   20.462  52937.8 3346.61
>  ptbtime3.ptb.de .PTB.            1 u  785 1024  377   43.870  56161.2 3384.54
>  ntp.nsm.pl      150.254.183.15   2 u  759 1024  377   47.775  52883.6 3359.28

Why in the world are you using 6 stratum 1 time sources? Quit it.  There
is absolutely no reason for that. 


>
>==============================================================================
> # NTP Network Time Protocol 
> # **** ATTENTION ****: *You have to restart the NTP service when you change this file to activate the changes* 
> # PLEASE CHECK THIS FILE CAREFULLY AND MODIFY IT IF REQUIRED 
> # Configuration File created by Windows Binary Distribution Installer Rev.: 1.26  mbg
> # please check http://www.ntp.org for additional documentation and background information
> # Use drift file 
> driftfile "D:\util\system\NTP\etc\ntp.drift"
>
> # your local system clock, should be used as a backup
> # (this is only useful if you need to distribute time no matter how good or bad it is)
> server 127.127.1.0

GET RID OF THIS. I have no idea why anyone would have put this local
server into a distributed ntp.conf file. It is simply stupid.

> # but it operates at a high stratum level to let the clients know and force them to
> # use any other timesource they may have.
> fudge 127.127.1.0 stratum 12 
>
> # Use specific NTP servers
> server bevtime1.metrologie.at iburst minpoll 8 maxpoll 10
> server ptbtime1.ptb.de iburst minpoll 8 maxpoll 10
> server bevtime2.metrologie.at iburst minpoll 8 maxpoll 10
> server ptbtime2.ptb.de iburst minpoll 8 maxpoll 10
> server time.metrologie.at iburst minpoll 8 maxpoll 10
> server ptbtime3.ptb.de iburst minpoll 8 maxpoll 10
> server 0.europe.pool.ntp.org iburst minpoll 8 maxpoll 10
> #server time-a.timefreq.bldrdoc.gov iburst minpoll 8 maxpoll 10
> #server time-c.timefreq.bldrdoc.gov iburst minpoll 8 maxpoll 10

And you got all of these from where? And Why? 
Just use pool servers. Windows cannot keep great time anyway:-)




More information about the questions mailing list