From owner-freebsd-isp Wed Aug 14 07:59:43 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA03784 for isp-outgoing; Wed, 14 Aug 1996 07:59:43 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA03778 for ; Wed, 14 Aug 1996 07:59:39 -0700 (PDT) Received: from tahoma.cwu.edu (skynyrd@tahoma.cwu.edu [198.104.67.25]) by pahtoh.cwu.edu (8.6.13/8.6.9) with ESMTP id HAA20791; Wed, 14 Aug 1996 07:59:26 -0700 Received: (from skynyrd@localhost) by tahoma.cwu.edu (8.6.13/8.6.9) id HAA09380; Wed, 14 Aug 1996 07:59:22 -0700 Date: Wed, 14 Aug 1996 07:59:21 -0700 (PDT) From: Chris Timmons To: Sonja Jo Krenz-Bush cc: freebsd-isp@FreeBSD.ORG Subject: Re: INN problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hmmm... inn is a notorious memory hog. What is your HW config? How much physical memory? swap? Which release of FreeBSD are you running? Probably 96MB physical is a minimum for inn with anything near a full feed and a bunch of clients. -Chris On Wed, 14 Aug 1996, Sonja Jo Krenz-Bush wrote: > We've been having problems with inn just up and dying lately, ie, it just > stops running. The only thing that shows up in the log files are error > messages like the ones below. We tried upgrading to inn1.4unoff4 and > that hasn't seemed to help at all. > > Aug 8 13:56:51 brockman innd: ME cant remalloc 7430400 bytes Cannot > allocate memory > Aug 13 19:04:41 brockman innd: ME cant remalloc 4374784 bytes Cannot > allocate memory > Aug 14 04:41:04 brockman innd: ME cant remalloc 9429248 bytes Cannot > allocate memory > > Has anybody had a problem like this, or have any idea whats going on? > > Thanks for any help. > > > > > Sonja Jo Krenz-Bush ServNet/Abstract Software > sjkb@abstractsoft.com http://www.serv.net/~begonia > ``Just another one of the flock following the herd.'' >