From owner-freebsd-stable Fri Jan 26 20: 2:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clmboh1-smtp3.columbus.rr.com (unknown [65.24.0.112]) by hub.freebsd.org (Postfix) with ESMTP id 0959B37B401 for ; Fri, 26 Jan 2001 20:01:54 -0800 (PST) Received: from mail.iowna.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38]) by clmboh1-smtp3.columbus.rr.com (8.11.2/8.11.2) with ESMTP id f0R3xWr20429 for ; Fri, 26 Jan 2001 22:59:33 -0500 (EST) Message-ID: <3A72474D.979B84FA@mail.iowna.com> Date: Fri, 26 Jan 2001 22:58:05 -0500 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Problems with BIND in 4.2-STABLE (resource leak?) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having trouble with BIND in 4.2-STABLE (Jan 18 22:16:33) I'm running the version of BIND that installs by default (named -v reports 8.2.3-T6B) This machine is a firewall/email/web server. The DNS is currently running as a local cache - although I have a reverse lookup file to resolve the private IPs on the network. Here's what's happening. On startup a listing in "top" shows named using around 5M of memory and minimal processor usage. Under normal circumstances this doesn't seem to vary much. However, occasionally (I have yet to find out what triggers this) named will go psycho. CPU utilization will max out and the size of the process will bloat up to 15M. When this happens a "kill -HUP" will bring the CPU usage back to a sane level, but the program remains bloated to 15M. All the while, named seems to be answering queries just fine. A slowdown is noticable when the processor usage is maxed out, however. Has anyone else seen this, or have I got some unique problem here? Currently I have a cronjob doing a "killall -HUP named" every 6 hours which is at least keeping the CPU usage sane, and the machine has enough RAM that the 15M usage doesn't cripple it in the slightest. This behavious makes me nervious, however, and I'd like to resolve it as quickly as possible. I asked about this on -questions and got no response, so I'm starting to wonder if nobody else has seen this. Any information, including a "me too" would be helpful. If you'd like more data on the hardware type or details of the config, just ask. -Bill Moran To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message