Bind 9.3.0 on FreeBSD 5.3 exits with signal 11

This is a discussion on Bind 9.3.0 on FreeBSD 5.3 exits with signal 11 within the Bind Users forums, part of the DNS and Related Forums category; Hi, I've got a problem with Bind9.3.0 under the following circumstances: - Server: Sun Fire V65x, 2 x ...


Go Back   Usenet Forums > DNS and Related Forums > Bind Users

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 01-19-2005
Dirk Janssen
 
Posts: n/a
Default Bind 9.3.0 on FreeBSD 5.3 exits with signal 11

Hi,

I've got a problem with Bind9.3.0 under the following circumstances:

- Server: Sun Fire V65x, 2 x Xeon 2,8Ghz (Running with Hyperthreading), 2 GB=

Ram
- OS: FreeBSD 5.3-STABLE, interface configured with two IPs
- 2 completly seperated instances of Bind 9.3.0 compiled from source,=
running
with uid bind and each listening on a different ip
- I've compiled bind with the following options:
--prefix=3D/usr/local/bind9/bind9-res1 \
--exec-prefix=3D/usr/local/bind9/bind9-res1 \
--with-openssl=3Dno

The Server is one of our caching-only-nameservers (serves only 3 zones and=
does
recursion otherwise) for our customers (in use for just about 3 days) and=
each
instance of bind processes about 500-1000 queries/s.
Everything works fine so far, but there is one major problem:
The instances of named exit with signal 11 and coredump approximately every=

14-18 hours always at times when the cache of each named has grown about 550=
mb
and the queries are at their peak (max. 1000 queries/s). What I've done so=
far
is to limit the max-cache-size to 500 mb and modify
recursive-clients/tcp-clients but without any effort.
Here are the relevant parts of the options-statement:

++++++++++++++++++++++++++++++++++++++++++
options {
listen-on { xxx.xxx.xxx.xxx; };
listen-on-v6 { none; };
directory "/usr/local/bind9/bind9-res1";
pid-file "named.pid";
allow-query { known_hosts; !any; };
allow-transfer { trusted; !any; };
blackhole { block; };
notify no;
recursive-clients 5000;
tcp-clients 500;
querylog no;
max-cache-size 500M;
};
++++++++++++++++++++++++++++++++++++++++++

Another thing that I've encountered with this version of bind is that if the=

cache has grown approximately every hour each instance of bind comsumes=
around
95% CPU for a short period (estimated 1-2 minutes) which produces a high=
load on
the server. During this time named answers only a limited number of queries=

(around 100-200 queries/s), the others probably will timeout.

Has anybody an idea to solve this issue? Any help or hints would be=
appreciated.

Kind Regards,

Dirk






Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 06:31 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0