Re: ntpd problem - really nptdate problem

["Donald R. Spoon" <dspoon@satx.rr.com>]

martin f krafft <madduck@madduck.net> wrote:

> hi folks,
> why does my ntpdate fail to sync with a stratum 2 ntp server? if you
> ask me, it all looks correct. at l;east i can't find the error. please
> help!
>
> fishbowl:/etc# ntpdate -q ntp
> server 192.168.14.1, stratum 2, offset 7.054936, delay 0.02559
> 1 Aug 09:02:20 ntpdate[16221]: no server suitable for synchronization found
>
> fishbowl:/etc# ntpdate -d ntp
>  1 Aug 09:03:09 ntpdate[16226]: ntpdate 4.1.0 Mon Mar 25 23:39:50 UTC 2002 (2)
> transmit(192.168.14.1)
> receive(192.168.14.1)
> transmit(192.168.14.1)
> receive(192.168.14.1)
> transmit(192.168.14.1)
> receive(192.168.14.1)
> transmit(192.168.14.1)
> receive(192.168.14.1)
> transmit(192.168.14.1)
> server 192.168.14.1, port 123
> stratum 2, precision -16, leap 00, trust 000
> refid [129.132.2.21], delay 0.02559, dispersion 0.00108
> transmitted 4, in filter 4
> reference time:    c0ef3a1b.bedfd694  Mon, Jul 29 2002  5:50:51.745

Note the difference between the "reference" time and the "originate 
timestamp" and the "transmit timestamp" below.  See copy of my machines 
response to this command at the end of this reply.

> originate timestamp: c0f35bb4.b6ef2c73  Thu, Aug  1 2002  9:03:16.714
> transmit timestamp:  c0f35bad.498e10cf  Thu, Aug  1 2002  9:03:09.287
> filter delay:  0.02599  0.02559  0.02560  0.02560 
>          0.00000  0.00000  0.00000  0.00000 
> filter offset: 7.424089 7.424962 7.425959 7.426953
>          0.000000 0.000000 0.000000 0.000000
> delay 0.02559, dispersion 0.00108
> offset 7.424962
> 1 Aug 09:03:09 ntpdate[16226]: no server suitable for synchronization found
>
> ntp:~# echo rl | ntpq
> status=00f4 leap_none, sync_unspec, 15 events, event_peer/strat_chg,
> version="ntpd 4.1.0 Mon Mar 25 23:39:47 UTC 2002 (2)",
> processor="i486",
> system="Linux2.4.18-qos+embryo", leap=00, stratum=2, precision=-16,
> rootdelay=95.939, rootdispersion=4548.155, peer=0,
> refid=swisstime.ee.ethz.ch,
> reftime=c0ef3a1b.bedfd694  Mon, Jul 29 2002  5:50:51.745, poll=4,
> clock=c0f35c1f.fbe45803  Thu, Aug  1 2002  9:05:03.983, state=4,
> offset=-1.664, frequency=-43.892, jitter=51.784, stability=0.002
>
> thanks,

Dunno it this has any bearing on your problem, but I have ntp timeserver 
on my home lan that appears to be working.  I played around with the 
commands you provided and here is my machine's response:

gandalf:~# ntpdate -d bilbo
 2 Aug 18:35:24 ntpdate[1047]: ntpdate 4.1.0 Mon Mar 25 23:39:50 UTC 
2002 (2)
transmit(192.168.10.3)
receive(192.168.10.3)
transmit(192.168.10.3)
receive(192.168.10.3)
transmit(192.168.10.3)
receive(192.168.10.3)
transmit(192.168.10.3)
receive(192.168.10.3)
transmit(192.168.10.3)
server 192.168.10.3, port 123
stratum 2, precision -17, leap 00, trust 000
refid [128.252.19.1], delay 0.02580, dispersion 0.00000
transmitted 4, in filter 4
reference time:    c0f591e0.414d7279  Fri, Aug  2 2002 18:18:56.255
originate timestamp: c0f595bc.40344c37  Fri, Aug  2 2002 18:35:24.250
transmit timestamp:  c0f595bc.30ed9168  Fri, Aug  2 2002 18:35:24.191
filter delay:  0.02592  0.02582  0.02580  0.02580
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.059554 0.059536 0.059534 0.059535
         0.000000 0.000000 0.000000 0.000000
delay 0.02580, dispersion 0.00000
offset 0.059534

Note the differences mentioned above in the "reference time", 
"originalte timestamp" and "transmit timestamp" entries.  BTW, "bilbo" 
is the home LAN's time server which is listed as a "stratum 2" server 
that is synched with a couple of public timeservers at some Universities 
around the states.  I am NOT running on UTC here for any of my computers.

I don't have any suggestions for correction, except to check out the 
following:

1.  Make sure you have stopped ntpd.. ntpdate will refuse to run if ntpd 
is running.
2.  Run ntpdate as root
3.  Check out the time setting in your computer's bios and make sure it 
is reasonably close to the correct time to start with.  It appears that 
something is off by a few days somewhere...
4.  Check out your DNS and/or hosts file to make sure that "ntp" is 
being converted into the correct IP... it looks like it is..
5.  Are other computers on the LAN working OK with this timeserver??
6.  Have you tried the "-b" option which forces stepping using 
settimeofday() instead of slewing via adjtime() in ntpdate?

Cheers & Good Luck!
-Don Spoon-