URGENT, PLEASE READ: 9.5.0-P1 now available

Chris Thompson cet1 at hermes.cam.ac.uk
Wed Jul 16 22:55:46 UTC 2008


On Jul 10 2008, I wrote:

>On Jul 10 2008, JINMEI Tatuya / 神明達哉 wrote:
>
>>For anyone experiencing this problem, I'd like to get the following
>>information:
>
>This is for the BIND 9.4.2-P1 nameservers running under Solaris 10_x86
>(SunOS 5.10 Generic_127112-10, in non-global zones, on a Sun X4100 M2,
>if any of that matters) which I mentioned before - we have had a couple
>more incidents overnight.
[... details omitted ...]

I probably ought to provide an update on this. We continued to have such
incidents with BIND 9.4.2-P1, so I changed out recursive nameservers to
BIND 9.4.3b2, although I really don't like having to run beta versions in
production. 

We have had no problems since then. Our named logging cuts off at level
"warning", so it is possible that if it were at level "info" we would be
seeing some of the messages mentioned in other postings.

Most of the time the file description consumption is well below 256, even
though it must be peaking well above that. I suspect that this is why we
haven't [yet!] seen anything like the failure with "rndc reconfig" mentioned 
elsewhere. 32-bit mode Solaris STDIO cannot use fd numbers >= 256, and 
AIUI named uses STDIO to read and write config/zone/journal files.

-- 
Chris Thompson
Email: cet1 at cam.ac.uk



More information about the bind-users mailing list