Brian Utterback wrote:
> This appears to be an attempt to configure a peer, based on the stack.
> This suggests that you have peer or server lines with hostnames on
> them. The fact that the attempt to configure the peer fails is
> interesting. If the address were not resolvable, then it would not
> even try.

Yes; I use "pool.ntp.org" and friends.  I just checked, and all of them
resolve nicely to IPv4 addresses.

> This leads me to suspect that the peer_config routine is
> rejecting it, and the most likely reason that I can think of is that
> there is no external interfaces configured.

I don't understand what "external interfaces" means in this context.  If
you're talking about IP interfaces, that's definitely not true.  We
wouldn't be having this conversation if it were true ... it's running on
the same host system as my email server, and those external interfaces
are how it talks to the world.

# ifconfig e1000g1
e1000g1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu
1500 index 3
        inet 75.150.68.97 netmask fffffff8 broadcast 75.150.68.103
        ether 0:4:23:a7:54:e7
# ifconfig bge0
bge0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500
index 2
        inet 192.168.254.1 netmask ffffff00 broadcast 192.168.254.255
        ether 0:e0:81:2a:ae:2d
#

Maybe "external interfaces" means something special for ntpd?

> You might try replacing the hostnames with they actual addresses. That
> should bypass the resolver process and make the errors more visible.
> After you replace the hostnames, restart and then run "ntpq -p".

I had to do "ntpq -4p" to get it to work; the new tools seem to be funny
about IPv6 loopback and my configuration.

But the command did succeed, and printed out the peers as expected.  It
looks like the log file spam may have stopped.  It's been 5 minutes
since I restarted ntpd, and no new error messages are coming out.

So why are names bad and numbers ok?

-- 
James Carlson         42.703N 71.076W         <carls...@workingcode.com>
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org

Reply via email to