BIND 9.5.0-P2 crash on solaris 8 : socket.c:2586: fatal error:
Milan Jurik
Milan.Jurik at Sun.COM
Tue Sep 9 18:58:37 UTC 2008
Hi Jeff,
the second define isn't needed, only FD_SETSIZE.
As for "ulimit", just check if your Bind processes has the limit set
(see output of "plimit".
Best regards,
Milan
Jeffrey Collyer pÃÅ¡e v út 09. 09. 2008 v 10:55 -0400:
> I have recompiled with
>
> -DFD_SETSIZE=8192 -DISC_SOCKET_FDSETSIZE=8192
>
> and set the shell script that starts bind with
> ulimit -n 8192.
>
> I'll see if I get any more crashes.
>
> Jeff
>
>
> JINMEI Tatuya / ç¥æéå wrote:
> > At Mon, 08 Sep 2008 12:56:13 -0400,
> > Jeffrey Collyer <jwc3f at virginia.edu> wrote:
> >
> >> Running bind 9.5.0-P2 with -DISC_SOCKET_FDSETSIZE=8192
> >> on Solaris 8, recently patched, on Sparc. Server is DNS only, on
> >> reasonably old hardware, and thus fairly busy most of the time.
> >>
> >> Got this in the the logs :
> >>
> >> named[9706]: [ID 873579 local4.crit] socket.c:2586: fatal error:
> >> named[9706]: [ID 873579 local4.crit] select() failed: Invalid argument
> >> named[9706]: [ID 873579 local4.crit] exiting (due to fatal error in library)
> >>
> >> and named had to be restarted. I know that there have been a few others
> >> reporting this on the list, but I wanted to add one to the frequency
> >> counter.
> >
> > I don't know much about Solaris 8, but from my experiences with other
> > versions of Solaris, it requires redefining FD_SETSIZE in order to use
> > a larger size of FD set for select(). Please try increasing
> > FD_SETSIZE directly, i.e., rebuild BIND9 with -DFD_SETSIZE=8192.
> >
> >
More information about the bind-users
mailing list