URGENT, PLEASE READ: 9.5.0-P1 now available

[Emery Rudolph]

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.

I guess what I am really searching for is solid guidance on this problem. It
seems that enough people have reported the same error enough that someone
should have a better handle on both the error and  a better understanding of
the root cause. It would seem easy enough to reproduce the error yourself
given the scope of the problem.

Pardon my impatience or shortness, but I am becoming frustrated (as are
many) that the errors are very commonly reported, but solid answers have not
been forthcoming. Is someone at ISC reproducing these errors?





On Thu, Jul 24, 2008 at 5:24 PM, JINMEI Tatuya / $B?@L at C#:H(B <Jinmei_Tatuya at isc.org>
wrote:

> At Thu, 24 Jul 2008 16:49:47 -0400,
> "Emery Rudolph" <emery.rudolph at gmail.com> wrote:
>
> > I am unsure what else you need, but I will be glad to supply it if you
> can
> > be specific.
>
> > > > I read at another source that although the processor will run high,
> the
> > > > server is not in danger of failing. Please confirm that this is true
> as I
> > > > need to make plans to both remedy this problem and upgrade another
> > > server.
>
> I'd specifically like to know:
>
> At Thu, 24 Jul 2008 16:49:47 -0400,
> "Emery Rudolph" <emery.rudolph at gmail.com> wrote:
>
> > > > Additionally - I just upgraded our secondary nameserver and am
> receiving
> > > the
> > > > same error. I am using Solaris 5.9 and have plenty of free resources
> and
> > > the
> > > > process limits are as follows:
> [...]
> > > > I read at another source that although the processor will run high,
> the
> > > > server is not in danger of failing. Please confirm that this is true
> as I
> > > > need to make plans to both remedy this problem and upgrade another
> > > server.
>
> - what's the same error
> - what you exactly meant by 'not in danger of failure'
>
> ---
> JINMEI, Tatuya
> Internet Systems Consortium, Inc.
>