innfeed problem

Russ Allbery rra at
Sat Jan 27 11:17:40 UTC 2001

Frans Dogge <newsmaster at> writes:
> At 03:24 PM 1/23/01 -0800, Russ Allbery wrote:

>> Everything looks fine with that; I don't see any obvious problems.  Are
>> you getting any log messages at all from innfeed?

> *sigh* I thought the same thing, but $pathlog/innfeed.log is completely
> empty.

It always is.  Check news.notice instead.  innfeed.log only contains the
rare completely fatal error message.

> And I don't understand what innfeed.status tells me.  Here is part of my
> innfeed.status log. It seems to reject most articles, bit I don't have a
> clue why.

> reader1
>    seconds: 8295      art. timeout: 600          ip name:
>    offered: 58570    resp. timeout: 300             port: 119
>   accepted: 22      want streaming: yes      active cxns: 1
>    refused: 58345     is streaming: yes    sleeping cxns: 0
>   rejected: 142         max checks: 25      initial cxns: 1

It looks like everything is working fine to me, just that most of the news
you're offering back the remote server already has.

Russ Allbery (rra at             <>

More information about the inn-workers mailing list