Richard Coleman
2005-May-22 14:10 UTC
can't assign requested address with ntpd on 5-STABLE
On 5-STABLE, when I try to start ntpd, I get the following error: bind() fd 7, family 28, port 123, addr fe80:1::2a0:c9ff:fec8:ea25, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address I've used netstat to check and nothing else is on that port (other than sshd, there is nothing else on the box). My ntp.conf line only has one line "server time-a.nist.gov". All other configuration for ntpd is the default. I googled for this error and got several hits. It was suggested to add the line "disable auth" to ntp.conf. But in this case I still received the same error. I'm am running a recent 5-STABLE box (built yesterday). The kernel is equivalant to GENERIC with the exception that I've commented out the I486_CPU and i586_CPU lines. Anyone else seen this recently. Richard Coleman rcoleman@criticalmagic.com
On Sun, 22 May 2005, Richard Coleman wrote:> On 5-STABLE, when I try to start ntpd, I get the following error: bind() > fd 7, family 28, port 123, addr fe80:1::2a0:c9ff:fec8:ea25, > in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address > > I've used netstat to check and nothing else is on that port (other than > sshd, there is nothing else on the box).This is normal; its trying to bind to the ipv6 address and you probably don't have one defined or have ipv6 disabled. It can be safely ignored. I think on later -STABLE its been disabled. Unless you _want_ to bind to the v6 address :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
On Sun, 22 May 2005, Richard Coleman wrote:> On 5-STABLE, when I try to start ntpd, I get the following error: bind() > fd 7, family 28, port 123, addr fe80:1::2a0:c9ff:fec8:ea25, > in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address > > Anyone else seen this recently.I've seen something similar with IPV4. Problem here was that I had multiple interfaces with the same address (an ethernet and some point-to-point interfaces that shared the same near-end address). ntpd appears to enumerate the interfaces and tries to bind (by address) to all of them, then fails because it's trying to bind the same thing twice. This isn't directly the same as your problem, but might be similar? Do you have alias addresses or something that may give the same effect?