[leafnode-list] Re: leafnode-2: fetchnews always says "0 articles posted"
matthias.andree at gmx.de
Sun Jun 3 19:46:19 CEST 2007
clemens fischer <ino-news at spotteswoode.dnsalias.org> writes:
> what actually happened was this: the article had not been posted at
> all, i found it in "failed.postings", then re-poted it by simply moving
> it over to "out.going".
Ah gee. Why did it go into failed.postings? I guess we need a counter
for failed postings as red flags...
> my logs date back a few weeks, but i cannot find any mention of posts!
> i got the log data from my tcpdump(1) log. the crontab entry:
> fetchnews -v
> which i just changed to
> fetchnews -vv >>/log/fetchnews.log 2>&1
> to get more information. how come posts, including failed ones, don't
> show up in the syslog? i noticed that the line "logstderr = 1" in
> etc/leafnode/config applies only to fetchnews, but not leafnode.
> currently, i have this knob turned off.
Yup, that's because some so-called "superservers" of the inetd kind were
reported to spit out stderr stuff over the wire, which isn't intended,
so leafnode suppresses this.
> but there's news: another article posted via gmane still in
> out.going went through using "fetchnews -vvv -n -P" and there it
> said "news.gmane.org: 1 articles posted". the dialog with the server
> basically went:
> 340 Ok, recommended ID <f3safa$4ps$1 at sea.gmane...>
> 240 Article posted (mailed to moderator)
So at least that one works. :-)
More information about the leafnode-list