[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [leafnode-list] fetchnews and logrotate?
On Mon, 19 Jan 2004 22:50:08 +0100, Matthias Andree wrote
> Mike Vanecek schrieb am 2004-01-19:
> > Why this message: "skipping group "alt.", invalid name (NULL component)?"
> "alt." is not "alt". Small dot, huge difference.
My eyes have a lot of floaters ... I just flat missed the dot.
> Does fetchnews complete without complaints?
> The log file size is euhm impressive, not to say inconvenient.
> Indeed, logging has been increased, and interestingly, ever since
> this was done, no complaints about lost articles any more...
> > Jan 19 13:02:19 www fetchnews: microsoft.public.pocketpc: last seen
> > article was 350319, server now has 342874-350319
> Something bad happened between these lines. The previous line has a
> limit (variable "last") of 350319, the next line of 350310.
> There is no code in fetchnews 1.9.49 that could cause such a change,
> no addition/subtraction of 9 or 10 to be found.
> This has all looks of a hardware fault: CPU, RAM, bus, or, if the
> machine is under memory pressure and swaps, also disk controller/cabling
Just for the heck of it I tried all the way back to .45. Did not see any real
difference. I did rebuild .49 from source and reinstall it. Also, the news log
rotation was cleaned. (I put in create_all_links = 1 in config for a different
One would think that if it were hardware, it would be showing up in other areas?
One theory ... if one starts fetchnews while the update process is still
running, could that cause a problem?
After all my looking, things seem to be a little better, but still see a few
Jan 19 21:15:46 www fetchnews: leafnode 1.9.49.rel: verbosity level is 0
Jan 19 21:15:47 www fetchnews: connected to 126.96.36.199:119, reply: 200
Jan 19 21:15:48 www fetchnews: news-west.newscene.com: 0 articles posted
Jan 19 21:15:48 www fetchnews: Reading server info from
Jan 19 21:15:49 www fetchnews: alt.os.linux.redhat: considering
articles 31972 - 31973
Jan 19 21:15:49 www fetchnews: alt.os.linux.redhat: killed 31972
(<Uk5YGebhcevk7589E143XVbS1SMt8jMM@xxxxxxxxxxxxxxx>), already fetched before
Jan 19 21:15:49 www fetchnews: alt.os.linux.redhat: killed 31973
(<pan.2004.01.19.20.04.48.96324@xxxxxxx>), already fetched before
Jan 19 21:15:49 www fetchnews: alt.os.linux.redhat: 0 articles fetched
(to 10115), 2 killed
*** Why does it consider this range and then find they were already fetched?
Jan 19 21:15:49 www fetchnews: linux.redhat: no new articles
*** Yet here, it see that there are no new articles. Why did it not see the
same thing in alt.os.linux.redhat?
Jan 19 21:15:49 www fetchnews: news.software.readers: considering
articles 170819 - 170819
Jan 19 21:15:50 www fetchnews: news.software.readers: killed 170819
(<s9tvzymshqhi$.1nfmk5yoi60z1$.dlg@xxxxxxxxxx>), already fetched before
Jan 19 21:15:50 www fetchnews: news.software.readers: 0 articles
fetched (to 19959), 1 killed
Jan 19 21:15:55 www fetchnews: connected to 188.8.131.52:119, reply: 200
Jan 19 21:15:55 www fetchnews: news.spamcop.net: 0 articles posted
Jan 19 21:15:55 www fetchnews: Reading server info from
Jan 19 21:15:55 www fetchnews: spamcop.help: considering articles 83766
Jan 19 21:15:56 www fetchnews: spamcop.help: 3 articles fetched (to
26167), 0 killed
Jan 19 21:15:57 www fetchnews: wrote active file with 54278 lines
Jan 19 21:15:57 www fetchnews: child has process ID 13017
The fetching seems to be consistent with the numbers contained in
leaf.node/groups. I am just surprised to see so many "already fetched before"
Is this just the nature of the way things work?
Thank you for your assistance and the hard work you do maintaining leafnode.
Both are definitely appreciated.
leafnode-list mailing list