Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.EDU.AU!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!usc!chi-news.cic.net!io.org!nobody
From: taob@ionews.io.org (Brian Tao)
Newsgroups: comp.unix.bsd.bsdi.misc,comp.protocols.tcp-ip.domains
Subject: named running out of memory and aborting?
Date: 13 Nov 1995 10:45:51 -0500
Organization: Internex Online (io.org) Data: 416-363-4151 Voice: 416-363-8676
Lines: 17
Distribution: inet
Message-ID: <487p7f$7ia@ionews.io.org>
NNTP-Posting-Host: flinch.io.org
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:1429 comp.protocols.tcp-ip.domains:8309
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.
Any ideas on what I can do to track down this problem? Many of
our customers (i.e., those who use Winsock) can only specify a single
name server, so if our main one dies, they call up our support desk
and tell us that the Internet is down. ;-)
--
Brian Tao (BT300, taob@io.org)
Systems Administrator, Internex Online Inc.
"Though this be madness, yet there is method in't"