Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news-peer.gsl.net!news.gsl.net!news-lond.gsl.net!news.gsl.net!news.grolier.fr!pressimage!world-net!not-for-mail From: "Eric Salomé" <salome@certix.fr> Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: News remalloc error Date: 15 Dec 1996 06:42:03 GMT Organization: Certix Lines: 55 Message-ID: <01bbea53$1a59d2a0$438002c2@pm0-67.sct.fr> References: <01bbe88a$3291d6d0$0d1711cb@tethys> NNTP-Posting-Host: 194.2.128.67 X-Newsreader: Microsoft Internet News 4.70.1155 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:5445 David Benn <dbenn@vision.net.au> a écrit dans l'article <01bbe88a$3291d6d0$0d1711cb@tethys>... > Someone recently asked a question here about a remalloc error in the Daily > Usenet report, and someone else quoted a section from the INN docs. > > The advice given was basically to: > > 1. Add "unlimit datasize" and possibly "limit openfiles 256". > 2. Increase the MAXDSIZ to 128M (options MAXDSIZ=134217728 in > the kernel config files. And hope you don't have any malloc bugs around or foolish daemons that just don't free memory when they should. You better have at least 128MB of real memory too. > Since we have had a similar problem on our site - actually it occurs in the > daily.news > script code which does overview database expiry it seems - I thought I'd > try some of these remedies. In fact I tried all of them and it made no > difference. The error persists. What I get in the Daily Usenet Report is: > > Can't remalloc 9249516 bytes, Cannot allocate memory > Renumbering active file. How lucky, error message from my last Daily Usenet Report was : Can't remalloc 110242276 bytes, Cannot allocate memory I believe the program running at that time was "expireover" (though it could be expirerm) "expireover" likes to put old .overview files in memory .... It counts heavily on your C compiler to initialize all static variables to zero when the program starts (hopefully most compilers sh(w)ould do that). Try to find out a bug that could lead to such a memory greed. Didn't find any....yet I have launched "expireover -a" to get my old .overview file to reflect the content of newsgroups directories. Some of them have an .overview file size of up to 21MB.. not more Can't find why expireover needs to be so greedy. Help welcome. > Now, on our system, the MAXUSERS kernel value is already 128. Any point in > pushing this higher? Yep, I pushed the value to 256 (and it seems to help to allow over 150 simultaneous connections to nnrp) Regards, Eric Salomé <salome@certix.fr>