[leafnode-list] Re: How to debug missing (not-fetched)

[Reiner Steib <4.uce.03.r.s@xxxxxxxxxxxxxx>]

On Thu, Aug 14 2003, Matthias Andree wrote:

> Reiner Steib <4.uce.03.r.s@xxxxxxxxxxxxxx> writes:
>> or shouldn't it be filtered at "XOVER" level?
>
> That's a violent (if you have little bandwidth, that is) bug. [...]
> Try this patch on top of what you have, it works for me.

I see filtering at "XOVER" level in the logs now.

But then, the first run of fetchnews took much longer as usual (sorry
for the long lines):

Aug 14 12:15:55 [...]: gnus.gnus-bug: last seen article was 51187, server now has 22998 - 51181
Aug 14 12:15:55 [...]: gnus.gnus-bug: switched upstream servers? 51187 > 51181
Aug 14 12:15:55 [...]: gnus.gnus-bug: considering 28184 articles 22998 - 51181, using XOVER
Aug 14 12:15:55 [...]: article 22998 <m0skRHT-00013tC@xxxxxxxxxxxx> rejected by filter (XOVER)
[ thousands of similar lines skipped ]
Aug 14 12:18:18 [...]: gnus.gnus-bug: XOVER: 27776 seen, 7 I have, 27768 filtered, 1 to get
Aug 14 12:18:18 [...]: gnus.gnus-bug: will fetch 1 articles
Aug 14 12:18:18 [...]: gnus.gnus-bug: 1 articles fetched (to 2809), 0 killed

Now some normal runs (left here for completeness):

Aug 14 13:30:08 [...]: gnus.gnus-bug: no new articles
Aug 14 14:23:33 [...]: gnus.gnus-bug: no new articles
Aug 14 15:30:07 [...]: gnus.gnus-bug: no new articles
Aug 14 16:16:35 [...]: gnus.gnus-bug: considering 6 articles 51182 - 51187, using XOVER
Aug 14 16:16:35 [...]: gnus.gnus-bug: XOVER: 1 seen, 0 I have, 0 filtered, 1 to get
Aug 14 16:16:35 [...]: gnus.gnus-bug: will fetch 1 articles
Aug 14 16:16:35 [...]: gnus.gnus-bug: 1 articles fetched (to 2810), 0 killed
Aug 14 17:22:08 [...]: gnus.gnus-bug: no new articles

Now it happened again:

Aug 14 18:20:30 [...]: gnus.gnus-bug: last seen article was 51188, server now has 22998 - 51181
Aug 14 18:20:30 [...]: gnus.gnus-bug: switched upstream servers? 51188 > 51181
Aug 14 18:20:30 [...]: gnus.gnus-bug: considering 28184 articles 22998 - 51181, using XOVER
Aug 14 18:20:30 [...]: article 22998 <m0skRHT-00013tC@xxxxxxxxxxxx> rejected by filter (XOVER)
[ thousands of similar lines skipped ]
Aug 14 18:22:40 [...]: gnus.gnus-bug: XOVER: 27776 seen, 8 I have, 27768 filtered, 0 to get
Aug 14 18:22:40 [...]: gnus.gnus-bug: all articles already there

Probably, all rejected articles are filtered because of "maxage = 2".
I definitively didn't switch my upstream server:

200 quimby.gnus.org InterNetNews NNRP server INN 2.2.2 13-Dec-1999 ready (posting ok).

Is it normal or possible, that the numbers on INN decrease, e.g.
because of canceled articles?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list