[ntp:questions] Re: linux ntp problem

Dale R. Worley worley at theworld.com
Wed Nov 12 03:27:54 UTC 2003


mzupan at meso.com (Mike Zupan) writes:
> And here is the result when trying to run ntpdate on the client
> 
> root at homer:~# ntpdate -qdv monitor     
> 10 Nov 15:57:28 ntpdate[18715]: ntpdate 4.1.2 at 1.892 Thu Sep 11
> 23:47:05 PDT 2003
>  (1)
> transmit(66.193.31.12)
> receive(66.193.31.12)
> transmit(66.193.31.12)
> receive(66.193.31.12)
> transmit(66.193.31.12)
> receive(66.193.31.12)
> transmit(66.193.31.12)
> receive(66.193.31.12)
> transmit(66.193.31.12)
> 66.193.31.12: Server dropped: strata too high
> server 66.193.31.12, port 123
***** > stratum 16, precision -16, leap 11, trust 000
> refid [0.0.0.0], delay 0.02583, dispersion 0.00000
> transmitted 4, in filter 4
> reference time:    00000000.00000000  Thu, Feb  7 2036  1:28:16.000
> originate timestamp: c35a7a38.f171f362  Mon, Nov 10 2003 15:57:28.943
> transmit timestamp:  c35a7a39.189efd86  Mon, Nov 10 2003 15:57:29.096
> filter delay:  0.02588  0.02583  0.02585  0.02583 
>          0.00000  0.00000  0.00000  0.00000 
> filter offset: -0.15315 -0.15316 -0.15314 -0.15315
>          0.000000 0.000000 0.000000 0.000000
> delay 0.02583, dispersion 0.00000
> offset -0.153160
> 
> 10 Nov 15:57:29 ntpdate[18715]: no server suitable for synchronization
> found
> 
> 
> I don't understand why its not working.

If I interpret this correctly, you are running ntpdate on 'homer', and
directing it to ask the NTP on 'monitor' for the time.  But the NTP on
'monitor' is running at stratum 16; see the line marked "***'.  Since
you've already picked out a set of servers, why don't you execute:

        ntpdate -qdv ntp.alaska.edu clock.isc.org \
            montpelier.ilan.caltech.edu nist1.aol-ca.truetime.com

Dale



More information about the questions mailing list