ntpd problems since upgrading to 5.3

[John]

On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote:
> Ian Moore wrote:
> > Hi,
> > Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting the 
> > following error on boot:
> > ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1
> > ::204:61ff:fe46:be89, in6_is_addr_multicast=0 flags=0 fails: Can't assign 
> > requested address
> > 
> > ntpd seems to be working from what I can see in it's log file, but I can't do 
> > anything with ntpq to check it. 
> > Wether I run it as my normal user or as root, running ntpq -p always gives:
> > ntpq: write to localhost.foo.com failed: Permission denied
> > 
> 
> I had once a problem with ntpd, when also running named. Some hostname
> resolution failed, because the servers were started in the wrong order.
> Are you also running named?
> 
> > Here is my ntpd entries in rc.conf:
> > ntpd_enable="YES"               # Run ntpd Network Time Protocol (or NO).
> > ntpd_program="/usr/sbin/ntpd"   # path to ntpd, if you want a different one.
> > ntpd_flags="-c /etc/ntp.conf -p /var/run/ntpd.pid"
> 
> I use:
>   ntpd_enable="YES"
>   ntpd_flags="-g"
> 
> > and the contents of ntp.conf:
> > server          210.48.130.204
> > server          augean.eleceng.adelaide.edu.au
> > driftfile       /var/db/ntpd.drift
> > logfile         /var/log/ntpd
> 
> And here I use:
>   driftfile /var/db/ntpd.drift
>   pidfile /var/run/ntpd.pid
>   server nr1.time.server
>   server nr2.time.server
>   server nr3.time.server

OK - this is interesting!

I have identical ntp.conf files on my 5.2.1 system and my 5.3-STABLE
system.  Guess what?  The 5.2.1 system works, and the 5.3-STABLE system
doesn't.  Not only that, but the clock on my 5.3-STABLE system is RACING.
It is going at almost twice as fast as real time.

Here's the ntp.conf file:
    # stratum 3 time server
    server 192.168.1.1

    driftfile /var/db/ntp.drift

In both cases, name resolution is working.  On the 5.2.1 system, ntpdc
shows:
ntpdc> peers
     remote           local      st poll reach  delay   offset    disp
=======================================================================
*dexter.starfire 192.168.1.52     3   64  377 0.00073  0.060184 0.00093
ntpdc>

On the 5.3-STABLE system, it ntpdc shows:
ntpdc> peers
     remote           local      st poll reach  delay   offset    disp
=======================================================================
=dexter.starfire 192.168.1.53    16   64    0 0.00000  0.000000 0.00000
ntpdc>

This shows that DNS is working fine, as the remote name is being
correctly resolved.  (I know I'm showing some of my IP numbers, but
it's all NAT).

I'm afraid something is broke!

Oh, and ntpdate works on the 5.3 system just fine (when ntpd isn't
running, of course).

The system that is running 5.3-STABLE was a good time keeper before
this update (4.9-STABLE).
-- 

John Lind
john at starfire.MN.ORG