[ntp:questions] Re: Question: Why does ntpd keeps a fixed difference from localhost ??

Ray Kao cr.kao at ever.com.tw
Fri Nov 14 04:35:05 UTC 2003


mike cook <michael.cook at wanadoo.fr> wrote in message news:<3FB176A5.9040708 at wanadoo.fr>...
> Ray,
> 
> The first odd thing is that your ntpdate -qd localhost is showing a very
> long time to response
> originate timestamp: c351ac7c.90e22000  Tue, Nov  4 2003 12:41:32.565
> transmit timestamp:  c351ac83.6f2d9000  Tue, Nov  4 2003 12:41:39.434
>   that's not far off 7 seconds.
> NTP is very efficient, and should return a response in a few milliseconds.
> 
> Also , your local clock is missing polls
>   LOCAL(0)        LOCAL(0)         3 l   67   64  377     0.00    0.000 
> 10.01
> that looks odd, is your system so heavily loaded with higher priority 
> tasks that ntpd isn't getting a look in?
> 
> Looking at your configuration you seem to be a sf12k domain , with one 
> of your SC's as the selected time source.
> You should look at the Sun Blueprint
> "Using NTP on Sun Fire 15k 12 Servers"
> 
> It says that you shouldnt be using slewalways. I've not looked at 12k
> configs for a while to see in what conditions that is valid.
> 
> http://wwws.sun.com/software/security/blueprints/#ntpsunfire12k15k
> 
> Also check bugs 4510625 and 4656724 .
> 
> Mike

Dear Mike,

  In fact, ntpdate -qd localhost responses in just 0.13 sec. It's very
soon.
And, the same symptom happens also on our other sun sparc platforms 
(Solaris
8). eg. Sun Netra X1

  It looks like a new bug of Solaris 8. Sun will provide new patch to
fix this
bug.

  But, The difference from "local ntp's clock" to "local system TOD"
doesn't to
too large to make sense. It's reasonable to differ about serval usec
because ntp daemon calculates the correct time and it takes serval
usec, but serval seconds is too large, isn't it?

/> time ntpdate -qd localhost
14 Nov 11:57:53 ntpdate[24453]: ntpdate 3-5.93e Mon Sep 20 15:45:30
PDT 1999 (1)
transmit(127.0.0.1)
receive(127.0.0.1)
transmit(127.0.0.1)
receive(127.0.0.1)
transmit(127.0.0.1)
receive(127.0.0.1)
transmit(127.0.0.1)
receive(127.0.0.1)
transmit(127.0.0.1)
server 127.0.0.1, port 123
stratum 3, precision -16, leap 00, trust 000
refid [210.59.157.40], delay 0.02583, dispersion 0.00000
transmitted 4, in filter 4
reference time:    c35ed107.b62ce000  Fri, Nov 14 2003 11:56:55.711
originate timestamp: c35ed147.690a4000  Fri, Nov 14 2003 11:57:59.410
transmit timestamp:  c35ed141.296f5000  Fri, Nov 14 2003 11:57:53.161
filter delay:  0.02608  0.02588  0.02585  0.02583
                   0.00000  0.00000  0.00000  0.00000
filter offset: 6.248237 6.248170 6.248163 6.248161
                   0.000000 0.000000 0.000000 0.000000
delay 0.02583, dispersion 0.00000
offset 6.248161

14 Nov 11:57:53 ntpdate[24453]: step time server 127.0.0.1 offset
6.248161 sec

real    0m0.13s
user    0m0.01s
sys     0m0.01s



More information about the questions mailing list