Overview Buffers just keep on growing...

[Donald Roeber]

On Wednesday, January 22, 2003, at 10:13  AM, Jeffrey M. Vinocur wrote:

>
> On Wed, 22 Jan 2003, Donald Roeber wrote:
>
>> A few weeks ago, we ran into a problem where our overview buffers were
>> full.
>
> Do you pass the "expireover" parameter to news.daily?  Perhaps you're 
> not
> expiring overview entries at all?  (Do you see any indication in the
> nightly email that overview entries are being expired?)
>

Yes, I'm passing 'expireover' to news.daily.  However, there may be a 
problem with it... This is from the tail end of my news.daily report:

---------

buffindexed.c:1601 Can't malloc 233234432 bytes: Not enough spacePost 
expiration status:

Server status:
Server running
Allowing remote connections
Parameters c 10 i 50 (24) l 1000000 o 4083 t 300 H 2 T 60 X 0 normal 
specified
Reserved Expiring process 406756
Readers follow enabled
Perl filtering enabled


Perhaps the buffindexed.c error is causing a problem with the 
expiration?  I'm not really sure how to test this.



>
>> running INN 2.3.3 on Tru64 5.1a. ovmethod is set to buffindexed, and I
>> have four 2GB buffers created.  We're bringing in about 350000 
>> articles
>> a day, and sending out about 165000.  Do I simply need more buffers?
>
> The key number is not how many articles come in, but how many articles 
> you
> retain at any given time in total.  Is that number stable, or growing?
>

Since the bulk of our articles are in CNFS buffers, I expect it'll be 
fairly stable.  However, we do have a few local groups using a 
tradspool, so it's really up to expire.ctl to keep that spool under 
control.

	
-- 
Donald Roeber
ISC Networking