[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[leafnode-list] Re: Fetchnews messages
Enrico Wiki wrote:
> On Fri, May 22, 2009 at 6:02 PM, clemens fischer wrote:
> I completely empty the news spool before each test, leaving just an
> empty tree, no files. Then a fewtchnews command line to create the
> group list. Then a fetchnews -N to retrieve a group. Just that,
> nothing else.
"Highly irregular ..." ("The Third Policeman", Flann O'Brian, propably on
bycicles, bull licenses or the county council). You're supposed to run
fetchnews from cron(8) or similiar. It knows the servers you want to
use from the central config-file and the groups from its interaction
with leafnode. Only if you need missing articles would you make it
retrieve them using "-N".
> Here is a new test.
> sudo fetchnews -vvvN sci.med.nutrition
> fetchnews mode: get articles, get headers, get bodies, post articles
> found 0 articles in in.coming.
> text.giganews.com: connecting to port nntp
> trying: address 22.214.171.124 port 119...
> connected: address 126.96.36.199 port 119.
> text.giganews.com: connected (200), banner: "200 Text.GigaNews.Com"
> text.giganews.com: checking for new newsgroups
> text.giganews.com: found 0 new newsgroups
> text.giganews.com: not posting, feedtype == none.
> sci.med.nutrition: considering 117209 articles 167107 - 284315, using XOVER
> sci.med.nutrition: XOVER: 103758 seen, 0 I have, 0 filtered, 103758 to get
> sci.med.nutrition: will fetch 103758 articles
> store: duplicate article <
Your user-agent breaks lines in a funny way. Using gmane.org myself to
read mailinglists, I don't get to see the original M-IDs and cannot look
at the original articles.
Giganews.com is broken: It ignores M-IDs replacing them with its own,
so fetchnews is unable to verify if articles got posted. You're not
posting in this case, but this could be some other giganews bug.
> store: no valid newsgroups
This shouldn't happen at all. The message is issued if store.c doesn't
see a proper "Newsgroups:" header. As the article comes from upstream
and isn't altered by fetchnews, I'd be inclined to point at giganews
> sci.med.nutrition: 101932 articles fetched (to 101933), 9 killed
> fetchnews: 101932 articles and 0 headers fetched, 9 killed, 0 posted, in
> 9403 seconds
Doesn't look that bad.
Whenever I spot "bad" articles not in my own spool, I try to get them
via "http://howardk.freenix.org/msgid.cgi?STYPE=msgid&MSGI=%s", with the
last "%s" replaced by "<message-id>".
> I will try the regular subscribe with a reader and will let you know.
> I seem to remember I already did it, with similar results, but I am
> not sure, so I'll try again anyway.
So far, you have seen only warnings, no serious errors, I guess.
leafnode-list mailing list