buffindexed: overview data is too large 55193

[Kathryn Hemness]

Thanks a bunch.  I think we'll give this a shot.

On Wed, 26 Mar 2008, Jeffrey M. Vinocur wrote:

> Date: Wed, 26 Mar 2008 17:40:04 -0400 (EDT)
> From: Jeffrey M. Vinocur <jeff at litech.org>
> To: inn-workers at isc.org
> Subject: Re: buffindexed: overview data is too large 55193
>
> On Wed, 26 Mar 2008, Kathryn Hemness wrote:
>
> > innd: [ID 584949 news.error] buffindexed: overview data is too large 55193
> >
> > I'm using CNFS for the articles and buffindexed for the overview and
> > my overview is nowhere near full:
>
> I'm no expert in buffindexed, but taking a look at the code, this is
> saying that an individual overview record is too large (cutoff is 8192),
> not that the database is full by any means.
>
> I would speculate that this could be an article with aberrant headers of
> some variety resulting in an overview record that is long.  Of course,
> it's difficult to tell because the error message doesn't give you much to
> go on.
>
>
> If you want to track this down, I think you could make the logging more
> useful by editing storage/buffindexed/buffindexed.c (line ~1523) from:
>
>     warn("buffindexed: overview data is too large %d", len);
>
> to
>
>     warn("buffindexed: overview data for %s is too large %d",
>         TokenToText(token), len);
>
>
> After recompiling / make update / restarting INN, you should start getting
> log messages with storage tokens, which you can feed to $pathbin/sm and
> have a look at the headers of e offending article.
>
>
> --
> Jeffrey M. Vinocur
> jeff at litech.org
>
>


--Kathy

============================================================
Kathryn Hemness                        kfhemness at ucdavis.edu
Infrastructure Services                phone: 530.752.6547
Campus Data Center & Client Services   fax:   530.752.9154