[leafnode-list] Re: 423 Bad article number, ?was Re: leafnode-2.0.0.alpha20061010a snapshot available

[ino-news@xxxxxxxxxxxxxxxxxxxxxxxxx (clemens fischer)]

On Fri, 1 Dec 2006 23:45:45 +0100 Martin wrote:

> On Fri, Dec 01, 2006 at 09:16:19PM +0100, clemens fischer wrote:
>
>> i'm getting lots of these lately, most of them related to gmane.org.
> 
> I first and only saw this on gmane.org.
> 
>> the situation on the wire is weird, as the server seems to offer
>> overview data but won't hand out the articles:
> 
> Who cares? fetchnews does not. The problem is: The only article to be
> fetched is not sent by the server.
> 
>> 2006-12-01_16:35:32.98216 GROUP gmane.comp.sysutils.supervision.general
>> 2006-12-01_16:35:33.02053 211 1304 46 1349 gmane.comp.sysutils.supervision.general
>> 2006-12-01_16:35:33.02871 XOVER 1349-1349
> 
> Only one article to fetch.

since i cannot check the article in question, i cannot offer but a
theory: many ezmlm-handled mailinglists are beeing spammed lately. this
article might be spam. gmane keeps its overview data, but refuses to
send it because it has been marked as spam.

i just tried to use the gmane web interface to get at that article, but
only get "connection refused".

> I guess in former times there was no possibility of returning zero
> articles without a severe problem. So the return value of getarticles()
> is checked for being zero or not. In case of being zero there's supposed
> to be some severe error, so fetchnews stops getting articles from the
> server:
> 
>> > +if (artno_server == 0) artno_server = -1;
>> >     return artno_server;
>> > }
> 
> This is a quick && dirty hackaround. Since then I had no other side
> effects, everything seems to work well. Be aware: There is the
> possibility of being "-1 articles fetched" or other strange occurences.

so the real fix would be to check if articles have been received from
this particular server at all and rather try to get articles from the
next group on it than switching to the next server, correct?  maybe fail
the server only after a (configurable) minimal number of errors or if
the current group is the only or last one on it.

i checked the logs carefully and found that mostly the
gmane.comp.sysutils.supervision.general group was responsible
for my problem, so i tricked leafnode by removing its entry in
news/interesting.groups/. voila: hundreds of new articles from gmane.org
showed up, so did the missing articles from the leafnode group.


regards, clemens

-- 
_______________________________________________
leafnode-list mailing list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
https://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/