What would make ntpd hang in BSD 8?

[Chuck Swiger]

Hi--

On Feb 17, 2010, at 11:50 AM, Peter Steele wrote:
> My ntp.conf looks like this:
> 
> # General Configuration
> server 0.us.pool.ntp.org
> server 1.us.pool.ntp.org
> server 2.us.pool.ntp.org
> server 3.us.pool.ntp.org
> 
> # Drift file
> driftfile /var/db/ntpd.drift

Wonderful: short and clear.  :-)

> The output from ntpq for the BSD 7 system is this:
> 
>     remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
> +169.229.70.183  169.229.128.214  3 u   40  512   37    7.921    9.170   8.836
> *208.75.88.4     192.12.19.20     2 u   43  512   37   12.049    8.224   8.168
> +217.160.254.116 209.51.161.238   2 u   38  512   37   55.111   -7.128  10.347
> +198.247.173.220 128.206.12.130   3 u   39  512   37   47.401   -1.149   3.659
> status=c624 sync_alarm, sync_ntp, 2 events, event_peer/strat_chg,
> version="ntpd 4.2.0-a Sun Feb 24 09:12:07 UTC 2008 (1)",
> processor="amd64", system="FreeBSD/7.0-RELEASE-p9", leap=11, stratum=16,
> precision=-20, rootdelay=0.000, rootdispersion=8.340, peer=25349,
> refid=INIT, reftime=00000000.00000000  Wed, Feb  6 2036 22:28:16.000,
> poll=4, clock=cf26c2d5.ea2b4541  Wed, Feb 17 2010 11:32:37.914, state=1,
> offset=0.000, frequency=-13.269, jitter=0.001, stability=0.000

That looks normal / good.

> and the output from the BSD 8 system is this:
> 
>     remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
> 169.229.70.183  .INIT.          16 u    -   64    0    0.000    0.000   0.002
> 208.75.88.4     .INIT.          16 u    -   64    0    0.000    0.000   0.002
> 217.160.254.116 .INIT.          16 u    -   64    0    0.000    0.000   0.002
> 198.137.202.16  .INIT.          16 u    -   64    0    0.000    0.000   0.002
> assID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
> version="ntpd 4.2.4p5-a (1)", processor="amd64",
> system="FreeBSD/8.0-CURRENT", leap=11, stratum=16, precision=-19,
> rootdelay=0.000, rootdispersion=0.000, peer=0, refid=INIT,
> reftime=00000000.00000000  Wed, Feb  6 2036 22:28:16.000, poll=6,
> clock=cf26c4d1.d21b33f1  Wed, Feb 17 2010 11:41:05.820, state=1,
> offset=0.000, frequency=-14.299, jitter=0.002, noise=0.002,
> stability=0.000, tai=0
> 
> The most obvious difference is the .INIT. entries, but there also appear to be several "0.0" type of entries that look suspicious. What do these imply?

It means this machine isn't seeing NTP traffic (yet), and is completely unsync'ed.  But DNS resolution worked, or you wouldn't be seeing IP addresses.  Maybe a firewall or routing problem?  Can you do:

  ntpq -p 217.160.254.116

...from this FreeBSD-8 machine and see .USNO. replying?

-- 
-Chuck