My 9.5.1-P3 exit suddenly.

2009-08-11 Thread BBB Kee
Hi, We have a intel solaris 9 and bind9.5.1-P3 inside it. The named suddenly stopped at this morning. Here is it left: .. 11-Aug-2009 06:09:14.466 general: error: failed to start watching FD (512): invalid file 11-Aug-2009 06:09:14.467 general: error: failed to start watching FD (512):

Re: My 9.5.1-P3 exit suddenly.

2009-08-11 Thread Dmitry Rybin
ulimit -a ? Looks like as max open file descriptor limit exceeded. On FreeBSD/Linux boxes I use MONIT (http://mmonit.com/monit/) то check and restart bind. BBB Kee wrote: Hi, We have a intel solaris 9 and bind9.5.1-P3 inside it. The named suddenly stopped at this morning. Here is it

Re: My 9.5.1-P3 exit suddenly.

2009-08-11 Thread Gordon Ewasiuk
I was getting the same results on a couple of Solaris 9 on x86 servers. During a code review, a coworker found some fairly major changes in how BIND does things between 9.5.0-P2 and 9.5.1-P3. We had to backport just the security fix from 9.5.1-P3 to 9.5.0-P2 to address the sock-pending_recv

Re: My 9.5.1-P3 exit suddenly.

2009-08-11 Thread BBB Kee
Hi, On Tue, Aug 11, 2009 at 7:01 PM, Dmitry Rybin kirg...@corbina.net wrote: ulimit -a ? Looks like as max open file descriptor limit exceeded. time(seconds)unlimited file(blocks) unlimited data(kbytes) unlimited stack(kbytes)8480 coredump(blocks) unlimited

Re: My 9.5.1-P3 exit suddenly.

2009-08-11 Thread BBB Kee
On Tue, Aug 11, 2009 at 7:26 PM, Gordon Ewasiuk gewas...@above.net wrote: I was getting the same results on a couple of Solaris 9 on x86 servers. During a code review, a coworker found some fairly major changes in how BIND does things between 9.5.0-P2 and 9.5.1-P3. We had to backport just