Return to BSD News archive
#! rnews 1654 bsd
Newsgroups: comp.unix.bsd.bsdi.misc,comp.protocols.tcp-ip.domains
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!in1.uu.net!spcuna!spcvxb!terry
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Subject: Re: named running out of memory and aborting?
Nntp-Posting-Host: spcvxa.spc.edu
References: <487p7f$7ia@ionews.io.org>
Sender: news@spcuna.spc.edu (Network News)
Organization: St. Peter's College, US
Date: Mon, 13 Nov 1995 22:05:56 GMT
Message-ID: <1995Nov13.180556.1@spcvxb.spc.edu>
Lines: 16
Distribution: inet
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:1452 comp.protocols.tcp-ip.domains:8347
In article <487p7f$7ia@ionews.io.org>, taob@ionews.io.org (Brian Tao) writes:
> I have a BSD/OS 2.0 server running BIND 4.9.3-BETA17. It handles
> primary name service for 92 domains (besides our own), RADIUS
> authentication and staff logins. Once or twice a week, named dies and
> syslog reports "savedata: malloc: Cannot allocate memory - ABORT" or
> "savename: malloc: Cannot allocate memory - ABORT". The machine has
> 64 megs physical RAM and 128 megs swap. 35% swap usage is normal, so
> there's lots of it left. The named process itself occupies about 11
> megabytes after running for a few days.
Did you put "limit datasize 64m" in your named.boot file? Also, if that
doesn't help, try running 4.9.3-beta26 (or whatever version is latest).
Terry Kennedy Operations Manager, Academic Computing
terry@spcvxa.spc.edu St. Peter's College, Jersey City, NJ USA
+1 201 915 9381 (voice) +1 201 435-3662 (FAX)