Re: Leafnode timing out on news server that works with a news client.
Steve A wrote:
> Run leafnode in full verbose mode to see what's happening. Then you should
> see what the "previous condition" is.
I added "-vv" to fetchnews in /etc/news/leafnode/do-fetch-news and got this
mail.
text.news.blueyonder.co.uk: connecting to port nntp...
text.news.blueyonder.co.uk: connected.
text.news.blueyonder.co.uk: using STAT <message-ID> command.
text.news.blueyonder.co.uk: 0 articles posted.
text.news.blueyonder.co.uk: getting new newsgroups
text.news.blueyonder.co.uk: got 0 new newsgroups.
text.news.blueyonder.co.uk: reading server info
from /var/spool/news/leaf.node/text.news.blueyonder.co.uk
Merging in /var/spool/news/leaf.node/text.news.blueyonder.co.uk~ from
previous run
alt.religion.kibology: considering articles 48065 - 48078
alt.religion.kibology: 13 articles fetched, 1 killed
news.answers: no new articles
news.announce.newusers: no new articles
news.newusers.questions: no new articles
news.groups.questions: no new articles
news.software.readers: considering articles 21161 - 21162
news.software.readers: 2 articles fetched, 0 killed
alt.test: considering articles 267867 - 268263
Server disconnection or timeout before article could be retrieved #1
Warning: aborting fetch from text.news.blueyonder.co.uk due to previous
condition.
text.news.blueyonder.co.uk: conversation completed, disconnected.
wrote active file with 8171 lines
Started process to update overview data in the background.
Network activity has finished.
The previous messages since increasing the verbosity indicate the same
problem with alt.test. Is that group just too big for leafnode/fetchnews
to handle?
> I've run into this once, I seem to recall it can be a previous instance of
> Leafnode running. Did you check running processes ?
$ ps aux|grep news
adam 489 0.0 0.0 3588 572 pts/0 R+ 16:16 0:00 grep news
$ ps aux|grep node
adam 491 0.0 0.0 3588 572 pts/0 R+ 16:16 0:00 grep node
Reply to: