[leafnode-list] Upgrade to 1.11.3.rel-2 (Debian pkg) has brought back processes that don't stop.

Adam Funk adam00f at ducksburg.com
Wed Jul 6 13:11:05 CEST 2005


On Wednesday 06 July 2005 11:03, Matthias Andree wrote:

> Interesting. According to the Debian changelog, only the debconf text
> translations have changed.

That's what I thought.

> > For now I've downgraded back to 1.11.3.rel-1.  Should I file a
> > Debian bug report?

The problem didn't go away!

> The debug method is still the same. Please try to get the

I should have time to try this next week.  In the meantime I have some 
intermediate bits of information that I hope will be of interest.

Right now the processes are still alive:
# ps aux|grep news
news     14159  0.0  0.1   4488  1228 ?        Ss   11:38   0:00 /bin/sh -c if [ -x /etc/news/leafnode/do-fetch-news ]; then /etc/news/leafnode/do-fetch-news; fi
news     14161  0.0  0.1   4492  1260 ?        S    11:38   0:00 /bin/sh /etc/news/leafnode/do-fetch-news
news     14163  0.0  0.3   4612  3004 ?        S    11:38   0:00 /usr/sbin/fetchnews

but not doing anything:

$ find /var/spool/news/ -mmin -20
/var/spool/news/leaf.node

$ grep news /var/log/syslog
...
Jul  6 11:38:05 garcia fetchnews[14163]: comp.ai.philosophy: considering articles 34322 - 34372 
Jul  6 11:38:06 garcia fetchnews[14163]: comp.ai.philosophy: will fetch 48 articles
Jul  6 11:39:06 garcia fetchnews[14163]: < (ERROR: timeout - no response in 60 s)
Jul  6 11:48:01 garcia /USR/SBIN/CRON[14291]: (news) CMD (if [ -x /etc/news/leafnode/do-fetch-news ]; then /etc/news/leafnode/do-fetch-news; fi)
Jul  6 11:48:01 garcia fetchnews[14296]: leafnode 1.11.3.rel: verbosity level is 0, debugmode is 0
Jul  6 11:48:06 garcia fetchnews[14296]: Cannot obtain lock file, aborting.


But even though the server timed out, the connection is still open 
according to "netstat -a"
tcp        0      0 garcia:38365            text.news.blueyond:nntp ESTABLISHED

And the running fetchnews never tried the second server in my 
config file.  I think the problem is that the timeout is not 
closing the connection.



More information about the leafnode-list mailing list