inn2.4.1, expire running > 2 days on a feeder

[Bill Davidsen]

Miquel van Smoorenburg wrote:
> In article <Pine.LNX.4.61.0409230256180.11485 at potato.cts.ucla.edu>,
> Chris Stromsoe  <cbs at cts.ucla.edu> wrote:
> 
>>Starting about a week ago, expire started running for several days at a 
>>time.  It used to run for 6 or 7 hours.  At some point, history crossed 
>>the 2gb boundary.  That may or may not have anything to do with it.  inn 
>>was built with --enable-largefiles.  The machine is running debian 
>>"testing" linux.
>>
>>spool is cnfs, and overview is disabled.  news is stored in 3 x 10Gb 
>>buffers, 1 x 40Gb buffer, and 1 x 5Gb buffer, on a single jfs partition 
>>built from a 4 disk scsi raid5 with no spare.  ~news/db/ is on the same 
>>partition.
>>
>>expire was killing performance, so I killed it.  Any ideas about what to 
>>look for to figure out what's wrong?
> 
> 
> You probably need more memory. I/O from incoming/outgoing feeds
> is throwing away the existing cached history file, etc.

I got this advice as well with my similar problem. But since I have it 
on only one of six identical servers, and the other five expire in less 
than two hours, I have to think there's another cause.

I sure hope so, I am unlikely to get funding for more memory unless I 
can explain why it's a problem on only one machine!

-- 
    -bill davidsen (davidsen at tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me