URGENT, PLEASE READ: 9.5.0-P1 now available

[Emery Rudolph]

Milan,
After getting more information I see that the 65535 limit I was seeing for
the FD_SETSIZE limit is strictly for 64-bit applications. I will try the
recommended path of setting the 32-bit value to 4096 and recompiling BIND.

The one thing that bothers me is that Walter Gould (an earlier contributor
to this thread) is also running Solaris 9, has the exact same error and
tried the recommended modification and recompile only to wind up with
continued crashes. I will not make too strong a correlation, because there
are other variables such as system hardware that could be the cause.

In any case I will move forward and reply with the results.

Thanks,

Emery

On Fri, Jul 25, 2008 at 3:56 AM, Milan Jurik <Milan.Jurik at sun.com> wrote:

> Hi Emery,
>
>
> > The error ( a constant relentless swarm of these messages ) :
> >
> -----------------------------------------------------------------------------------
> > Jul 24 15:06:32 ns2 named[142]: [ID 873579 daemon.error] general: error:
> > socket: too many open file descriptors
> >
> ------------------------------------------------------------------------------------
> >
> > It is my understanding that this error is not necessarily fatal if the
> > number of open ports is relatively stable ( <1000) and the system has
> > sufficient resources. Please clarify if this error is fixable in Solaris
> 9.
> > I have read other threads which indicate the problem was solved by
> > recompiling BIND after increasing the FD_SETSIZE limit, but on Solaris
> this
> > limit is already at 65535, so it seems this may work on Linux based
> systems
> > - not Solaris.
> >
>
> Not exactly. plimit shows amount of available file descriptors per
> process. But FD_SETSIZE is different beast, specific to some libc
> functions. And by default FD_SETSIZE is 1024. Because you are using own
> Bind 9, you must recompile Bind with higher FD_SETSIZE.
>
> Best regards,
>
> Milan
>
>