From owner-freebsd-hackers  Tue Aug 26 09:22:00 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA18847
          for hackers-outgoing; Tue, 26 Aug 1997 09:22:00 -0700 (PDT)
Received: from dopey.pathlink.com (dopey.pathlink.com [204.30.237.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA18826
          for <freebsd-hackers@freebsd.org>; Tue, 26 Aug 1997 09:21:53 -0700 (PDT)
Received: from dvl-1.pathlink.com (dvl-1.pathlink.com [204.30.237.241])
	by dopey.pathlink.com (8.8.6/8.8.7) with SMTP id JAA10060;
	Tue, 26 Aug 1997 09:15:43 -0700 (PDT)
Message-Id: <199708261615.JAA10060@dopey.pathlink.com>
To: scrappy@hub.org
Subject: Re: [HACKERS] innd remalloc failure *after* setting MEMDSIZ
Cc: freebsd-hackers@freebsd.org
From: kachun@zippo.com (Kachun Lee)
Date: Tue, 26 Aug 1997 09:21:07 -0700
X-Mailer: WinVN 0.99.8 (x86 32bit)
In-Reply-To: <5to7ek$c4m@news.pathlink.com>
References: <Pine.BSF.3.95.970817210142.27023X-100000@alive.znep.com> <5to7ek$c4m@news.pathlink.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <5to7ek$c4m@news.pathlink.com>, you say...
>
>On Sun, 17 Aug 1997, Marc Slemko wrote:
>
>> On Sun, 17 Aug 1997, The Hermit Hacker wrote:
>> 
>> > 
>> > Hi...
>> > 
>> >     After going through "the archives", and finding the suggestion of 
increasing
>> > MEMDSIZ to 256Meg, and recompiling/running the new kernel...I'm still 
getting
>> > the remalloc 'crash' with innd.
>> > 
>> >     The kernel is 2.2.2-RELEASE, innd is 1.6b3...I have an 'unlimit' at 
the
>> > beginning of ~news/etc/rc.news...
>> 
>> What does a ulimit -a run from rc.news after your unlimit say?
>> 
>> It should be MAXDSIZ; was the just a typo, or did you set the wrong thing?
>
>        typo :(  Just checked, and it was MAXDSIZ that I sent...
>
>> What does the inn log report?
>
>        Just the remalloc() error, which varies for each time it happens...
>
>
>Marc G. Fournier                                
>Systems Administrator @ hub.org 
>primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 

remalloc error is usually cause by the channel feed processes (the Tc in the 
newsfeeds file) not keeping up. The common ones are overchan, overview, 
nntplink and innfeed. Let your innd run for several hours and do a 'ctlinnd 
flush <feed-name>' on each of your Tc feeds, and see if any one writes a 
backlog file in your out.going directory.