Date: Fri, 20 Mar 1998 05:52:40 +0200 (SAT) From: John Hay <jhay@mikom.csir.co.za> To: bsd@birdland.rhein-neckar.de (Martin Jangowski) Cc: isp@FreeBSD.ORG Subject: Re: Slooow expires (inn 1.5.1 and 1.7.2.insync1.1d) Message-ID: <199803200352.FAA00972@zibbi.mikom.csir.co.za> In-Reply-To: <Pine.BSF.3.94.980319225157.2059C-100000@birdland.rhein-neckar.de> from Martin Jangowski at "Mar 19, 98 10:56:14 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > I think you just went over some limit and now the database isn't > > handled in RAM anymore but on disk. It might be not enough RAM > > or the limits in login.conf might be too low or something like > > that. Try running /usr/bin/limits out of cron the same way your > > expiry is done and have a look at its output. > > I tried this with _lots_ of free memory. After rebuilding the .pag and > .dir files it used virtual memory. Something in the .dir file was the > culprit, I think. I was happy to have our newsserver up and running again, > so I didn't investigate. > > The same thing happened twice, and got resolved the same way, I'm fairly > sure that something in the dbz-files was corrupted. Was your limits set high enough? What was the size of your .pag file? Maybe bigger than what your limits allow you to have in memory? The reason doing a makehistory help is because it shrink your database to only the articles you have in your spool. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803200352.FAA00972>