[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[leafnode-list] Fetch taking an incredibly long time



I have been using leafnode for a couple of years here, starting with
v1.4, and upgrading to v1.9.2 and then 1.9.4.

With the last 2 versions I have had a problem that everything runs
smootly for weeks/months but then leafnode gets 'stuck' spending hours
and hours on line. tcpdump shows loads of traffic with the upstream news
server but the fetchnews output just says 'Trying to connect to
news.demon.co.uk ...'

What is going on at this point? I left it on for over 6 hours to see if
it would become satisfied but no joy, then another 6 hours the next day.
I decided my phone bill was now more than enough and have stopped it
running for a month. I though maybe it was the periodic collecting of a
full list of groups, but that shouldn't take more than an hour or so (we
have a 64K ISDN line) should it?

This has happened before and I really need to be able to stop it. Apart
from this leafnode is great.

The system is redhat 5.1, kernel 2.0.36, i386.

Even if I tell leafnode not to collect any groups (by removing all files
from /var/spool/news/interesting.groups) it still sits there for hours
wurbling away.

Help! Any suggestions? Would a tcpdump help? 

I hope this isn't a stupid question but I couldn't find anything relevant
in the archive.

Wookey
-- 
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel (00 44) 1223 811679
work: http://www.aleph1.co.uk/     play: http://www.chaos.org.uk/~wookey/


-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list