NTP: ntpdate: Server dropped: strata too high

Tom Diehl tdiehl at rogueind.com
Fri Aug 1 17:39:36 UTC 2003


On Fri, 1 Aug 2003, Felipe Alfaro Solana wrote:

> On Fri, 2003-08-01 at 18:07, Tom Diehl wrote:
> 
> > > I have just set up an NTP server on a Taroon Beta 1 machine. The NTP
> > > server seems to be running, but when trying to do an "ntpdate" against
> > > it, the client receives the following error:
> > > 
> > 
> > Have a look at the server with ntpq. Once you start ntpq run the pe, as,
> > and rv commands and you should get an idea what is going on. It sounds
> > to me like your server is not synced. AN unsynced server is normally
> > strat 16.
> 
> The server should be synched, since upon starting "ntpd", the "ntpdate"
> command is invoked and the time is synched. At least, that's what is
> seems from looking at "/var/log/messages" and invoking "ntpdate"
> manually.
> 
> NOTE: I have had to modify "/etc/init.d/ntpd" because my firewall is
> preventing any UDP traffic from privileged (<1023) ports from passing
> through it. Thus, I've had to add the "-u" option to "ntpdate". Could
> this be affecting the NTP server? Is there any ntpd option to force
> usage of non-privileged source UDP ports?

You need port 123 udp open for ntp to function.

> I must say that I have no idea about NTP, so all of this is completely
> new to me. Here are is the output of "ntpq":
> 
> ntpq> pe
>      remote           refid      st t when poll reach   delay  
> offset    disp
> ==============================================================================
>  woon.curie.fr   0.0.0.0         16 u    -   64    0     0.00    0.000
> 16000.0
>  xoon.curie.fr   0.0.0.0         16 u    -   64    0     0.00    0.000
> 16000.0
>  lip.curie.fr    0.0.0.0         16 u    -   64    0     0.00    0.000
> 16000.0
>  time.nist.gov   0.0.0.0         16 u    -   64    0     0.00    0.000
> 16000.0
>  clock.redhat.co 0.0.0.0         16 u    -   64    0     0.00    0.000
> 16000.0

This indicates that your server is unable to talk to the time servers you wish to
sync with. The st column is the stratum of the server. The reach column is the 
number of seconds since the last time your server got a reply from the server
listed.

> ntpq> as
> ind assID status  conf reach auth condition  last_event cnt
> ===========================================================
>   1 44140  8000   yes    no
>   2 44141  8000   yes    no
>   3 44142  8000   yes    no
>   4 44143  8000   yes    no
>   5 44144  8000   yes    no

this says I cannot find the servers.

> ntpq> rv
> status=c011 sync_alarm, sync_unspec, 1 event, event_restart
> system="Linux", leap=11, stratum=16, rootdelay=0.00,
> rootdispersion=0.00, peer=0, refid=0.0.0.0,
> reftime=00000000.00000000  Thu, Feb  7 2036  7:28:16.000, poll=4,
> clock=c2d51d07.8b3aa000  Fri, Aug  1 2003 19:08:23.543, phase=0.000,
> freq=0.00, error=0.00

This among other things says your clock is stratum 16

> 
> What's really strange is how all the NTP servers from which time is
> synched are set an stratum of 16. For example, "woon.curie.fr" is really
> an stratum 1 server:
> 
> # ntptrace woon.curie.fr
> woon.curie.fr: stratum 1, offset 0.211136, synch distance 0.00000, refid
> 'GPS'
> 
> What's going on here? Any ideas?
> Thanks!

your not talking to the time servers. You MUST be able to talk to the
timeservers on port 123 udp otherwise it will not work.

Just for reference here is the pe output from one of my timeservers:
(icarus pts8) # ntpq
ntpq> pe
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+bonehed.lcs.mit .GPS.            1 u  668 1024  377   29.893   10.282   6.852
+NAVOBS1.MIT.EDU .PSC.            1 u  667 1024  377   29.669   10.152   0.075
*time.nist.gov   .ACTS.           1 u  696 1024  377  102.528   -2.858   5.146

Now as:
ntpq> as
ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1 26580  9434   yes   yes  none  candidat   reachable  3
  2 26581  9434   yes   yes  none  candidat   reachable  3
  3 26582  9634   yes   yes  none  sys.peer   reachable  3

Now rv:
ntpq> rv
status=06b4 leap_none, sync_ntp, 11 events, event_peer/strat_chg,
version="ntpd 4.1.1a at 1.791 Sat Aug 31 18:27:29 EDT 2002 (1)",
processor="i686", system="Linux2.4.20-19.8", leap=00, stratum=2,
precision=-17, rootdelay=102.528, rootdispersion=55.574, peer=26582,
refid=time.nist.gov,
reftime=c2d5211f.ef404ea4  Fri, Aug  1 2003 13:25:51.934, poll=10,
clock=c2d5240e.5ae88df3  Fri, Aug  1 2003 13:38:22.355, state=4,
offset=2.715, frequency=-130.203, jitter=29.472, stability=0.043

See the difference??


-- 
......Tom		Registered Linux User #14522	http://counter.li.org
tdiehl at rogueind.com	My current SpamTrap ------->	mtd123 at rogueind.com





More information about the fedora-test-list mailing list