Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Mar 2001 11:54:10 -0500
From:      "Michael R. Wayne" <wayne@staff.msen.com>
To:        "freebsd-isp@freebsd.org" <freebsd-isp@FreeBSD.ORG>
Subject:   Re: BIND 9.1.1rc2 and FreeBSD 4.2-stable
Message-ID:  <20010302115410.K24722@staff.msen.com>
In-Reply-To: <3A9EDD99.7DC1B1CE@staff.norlight.net>; from hyun@staff.norlight.net on Thu, Mar 01, 2001 at 05:39:05PM -0600
References:  <3A9EDD99.7DC1B1CE@staff.norlight.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 01, 2001 at 05:39:05PM -0600, Hyunseog Ryu wrote:
> 
> Hi, folks
>  
>  I have questions for BIND version 9.1.1rc2.
>  Recently I installed BIND 9.1.1rc2 into one of FreeBSD 4.2-stable
>  version.
>  After installation of BIND, it works fine for a while.
>  But when I look at the "top" command output, 
>  it says that memory consumption of named is increasing continuously.
>  Yesterday I saw that named consumed more than 67MB memory.

67MB is a reasonable size for named.   Your box has 256M, so don't
worry about it. 

>  And today named suddenly stopped to respond.
>  Do you guys have similar problem?
>  
>    PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU
> COMMAND
>  42818 dns        2   0 29472K 28528K poll    18:02 10.79% 10.79% named

>  I don't know what caused this problem.

This concerns me.  We had a similar problem with 9.1.0 where named
would stop responding (oddly, host continued to work but dig@localhost
hung).  Our interim fix was a script that ran every 5 minutes
checking for timeouts and restarting named if it hung.  After the
upgrade to 9.1.1rc2, we have not seen this problem.  And we serve
a LOT of dns since in addition to our clients we're a top level domain
server.

The problem is not specific to FreeBSD, we see it on BSD/OS as well.

I see you upgraded to rc3 recently, perhaps that will make a difference.

If you contact isc about this, you can reference ticket
   [ISC-Bugs #912] (bind9) 
since it sounds like the same problem.

Should this happen again, try to get a stack trace.  We're not getting
core files when we kill it.

/\/\ \/\/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010302115410.K24722>