[leafnode-list] Re: [1.11.6] HEAD 1234: reply 423 Bad article number

[Matthias Andree]

Am Donnerstag, den 13.09.2007, 23:26 +0200 schrieb Martin Klaiber:
> When I try to fetch some missing postings with fetchnews -x 3000, I get
> error-messages like these (from /var/log/syslog):
> 
>    Sep 13 23:00:17 wallace fetchnews[4157]: de.comm.software.newsserver HEAD 28988: reply 423 Bad article number (15 more up in the air)
>    Sep 13 23:00:17 wallace fetchnews[4157]: de.comm.software.newsserver HEAD 28989: reply 423 Bad article number (14 more up in the air)
>    Sep 13 23:00:17 wallace fetchnews[4157]: de.comm.software.newsserver HEAD 28990: reply 423 Bad article number (13 more up in the air)
>    Sep 13 23:00:17 wallace fetchnews[4157]: de.comm.software.newsserver HEAD 28991: reply 423 Bad article number (12 more up in the air)
>    ...
> 
> Is this a problem of the upstream-server (news.fu-berlin.de crashed
> about two weeks ago) or a problem of leafnode/fetchnews?

Upstream issue, XOVER data and actual article spool are inconsistent.
I've Bcc'd them - dear newsmasters, please consider rebuilding the XOVER
data. Thanks.

Best regards,

-- 
Matthias Andree <matthias.andree at gmx.de>