bind 9.4.3b2: too many open files

[JINMEI Tatuya / 神明達哉]

At Tue, 15 Jul 2008 12:44:38 +0200,
Tom Mueller <t.mueller at strato-rz.de> wrote:
> the first errors occured a short time after starting bind:
> 
> 15-Jul-2008 12:00:29.747 general: epoll_ctl(DEL,978), 4: Bad file descriptor
> 15-Jul-2008 12:00:29.747 general: epoll_ctl(DEL,978), 4: Bad file descriptor
> 15-Jul-2008 12:03:27.102 general: socket.c:523: unexpected error:
> 15-Jul-2008 12:03:27.102 general: socket.c:523: unexpected error:
> 15-Jul-2008 12:03:27.102 general: epoll_ctl(DEL,1470), 4: Bad file
> descriptor
> 15-Jul-2008 12:03:27.102 general: epoll_ctl(DEL,1470), 4: Bad file
> descriptor
> 15-Jul-2008 12:03:34.774 general: socket.c:523: unexpected error:
> 15-Jul-2008 12:03:34.774 general: socket.c:523: unexpected error:
> 15-Jul-2008 12:03:34.774 general: epoll_ctl(DEL,702), 4: Bad file descriptor
> 15-Jul-2008 12:03:34.774 general: epoll_ctl(DEL,702), 4: Bad file descriptor
> 15-Jul-2008 12:34:19.464 dispatch: dispatch 0xb5d0c008: odd socket
> result in udp_recv(): connection refused
> 
> The last message could be a result of invalid data received (??)

Could you try the attached patch(*)?  I believe it should at least fix
the 'bad file descriptor' problem.  It may also solve some other
issues you've seen, including the dispatch warning and the crash in
resolver.c, but I'm not sure about that: I've been thinking about a
possible scenario that combine the socket.c issue and the others, but
could not find anything yet.

(*) I've also copied the patch at
http://www.jinmei.org/socket.c.diff
so that others who are interested can test it (I'm afraid the ML
system will remove the attachment).

Thanks,

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.