socket.c error in bind 9.9.0b2

[Mark Andrews]

In message <4ECC3523.3070207 at gis.net>, Danny Mayer writes:
> On 11/22/2011 11:17 AM, Spain, Dr. Jeffry A. wrote:
> > When bind 9.9.0b2 starts up, the syslog shows the following messages:
> > 
> > Nov 22 10:18:19 nstest2 named[17190]: using default UDP/IPv6 port range: [1
> 024, 65535]
> > Nov 22 10:18:19 nstest2 named[17190]: listening on IPv6 interfaces, port 53
> > Nov 22 10:18:19 nstest2 named[17190]: socket.c:5728: unexpected error:
> > Nov 22 10:18:19 nstest2 named[17190]: setsockopt(513, IPV6_V6ONLY) failed: 
> Invalid argument
> > 
> 
> I suspect you ran out of available file descriptors. 513 is a suspicious
> number. Look to see what your file descriptor limit is. This version may
> be leaking file descriptors.
> 
> Danny

Known issue.  The socket is already bound so the setsockopt call
fails on the dup'd file descriptor.  You can ignore it.  A fix
is already on the review queue.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org