Problems starting inn

[Jeffrey M. Vinocur]

On Sep 26, 2005, at 10:17 AM, Iain Conochie wrote:

> Sep 26 14:55:12 pop-news innd: [ID 801587 news.crit] SERVER can't close
> history /data/news/db/history: File too large

How big -is- your history file?  Probably just reached 2 GB?


> After some net searching it seems that the history file is a list of 
> all
> news articles the server has dealt with, and is used for spotting
> looping messages (among other things). Will it be OK for be to blow 
> this
> file away and start the server i.e.
>
> cat /dev/null > /data/news/db/history

I wouldn't do that -- it will result in there being no way to access 
articles in your spool.

First we need to figure out what your longterm solution will be, and 
then figure out how to get there in the short term.

If you hit the size limit of your file system, your longterm options 
are to (1) adjust the size limit to allow bigger files, (2) reduce the 
number of history file lines for articles currently in your spool, or 
(3) reduce the number of history file lines for articles not in your 
spool but that you've already seen and expired or rejected.

#1 can be done by building with large file support, although the 
transition can be complicated.  #2 can be done by shortening expire.ctl 
times for tradspool or reducing the size of CNFS buffers.  #3 can be 
done by adjusting /expire/ in expire.ctl, although only with caution.

Telling us a little about how your articles are stored and what sort of 
expiration paramters you prefer will help us guide you.

-- 
Jeffrey M. Vinocur
jeff at litech.org