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

Re: [leafnode-list] Problems after upgrade to 1.9.33

To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [leafnode-list] Problems after upgrade to 1.9.33
From: Matt Gibson <gothick@xxxxxxxxxxxxxx>
Date: Sat, 22 Mar 2003 08:32:22 +0000
In-reply-to: <3E790011.BeroList-2.5.9@wpxx02.toxi.uni-wuerzburg.de>
Organization: The Wardrobe Happy Cow Emporium
Original-message-id: <200303220832.22953.gothick@gothick.org.uk>
Reply-to: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5

[Please let me know if these mails are getting too long; I don't want to drown 
the list in logfiles...]

Hullo again.  I'm afraid I'm still having the same strange problem.  After my 
last post, I added another verbosity level to the fetchnews invocation (I 
know it says in the manpage that the output won't necessarily make sense, but 
I was hoping for some clue...)

This moring, I connected to my news server, and it fetched only the articles 
for one group, demon.service.  I've omitted some of the repetitive output so 
as not to post huge amounts to the list, but this is basically what the log 
showed:

leafnode 1.9.36.rel: verbosity level is 4
Trying to connect to news.demon.co.uk:nntp ... connected.
Using STAT <message-ID> command on this server.
news.demon.co.uk: 0 articles posted
Getting new newsgroups from news.demon.co.uk
Reading server info from /var/spool/news/leaf.node/news.demon.co.uk
demon.service: considering articles 12820 - 12825
demon.service: will fetch 12820 
(/var/spool/news/message.id/514/<1fs3cmh.dnepz61307ml5N%me3@xxxxxxxxxxx>)
demon.service: will fetch 12821 
(/var/spool/news/message.id/809/<Kv$kk9W4g5e+Ewi+@xxxxxxxxxxxxxxxxxxxxxx>)
demon.service: will fetch 12822 
(/var/spool/news/message.id/310/<b5g7b8$29a77k$1@xxxxxxxxxxxxxxxxxxxxxxxx>)
demon.service: will fetch 12823 
(/var/spool/news/message.id/573/<MzpsvrI816e+EwzM@xxxxxxxxxxxxxxxxxxxx>)
demon.service: will fetch 12824 
(/var/spool/news/message.id/241/<XR7ex0CLkAf+Ew6F@xxxxxxxxxxxxxxxxxxx>)
demon.service: will fetch 12825 
(/var/spool/news/message.id/636/<ld7CQ4Ban1e+EwEm@xxxxxxxxxxxxxxxxxxxxx>)
[*SNIP* -- first five articles retrieved]
demon.service: receiving article 12825 (0 more up in the air)
..saw header Path: 
..saw header From: 
..saw header Newsgroups: 
..saw header Subject: 
..saw header Date: 
..saw header Lines: 
..saw header Message-ID: 
..saw header References: 
..saw header Xref: 
storing <ld7CQ4Ban1e+EwEm@xxxxxxxxxxxxxxxxxxxxx>: demon.service
.as article 256 in demon.service
demon.service: 6 articles fetched, 0 killed
uk.local.southwest: considering articles 9190 - 9196
uk.local.southwest: will fetch 9190 
(/var/spool/news/message.id/700/<b5g3u5$egc$1@xxxxxxxxxxxxxxxxxxxx>)
uk.local.southwest: will fetch 9191 
(/var/spool/news/message.id/703/<b5g3u7$egc$2@xxxxxxxxxxxxxxxxxxxx>)
uk.local.southwest: will fetch 9192 
(/var/spool/news/message.id/861/<b5g6f8$ndt$1@xxxxxxxxxxxxxxxxxxxx>)
uk.local.southwest: will fetch 9193 
(/var/spool/news/message.id/687/<TwOea.229$595.127@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>)
uk.local.southwest: will fetch 9194 
(/var/spool/news/message.id/122/<b5gcgo$dcp$1@xxxxxxxxxxxxxxxxxxxxx>)
uk.local.southwest: will fetch 9195 
(/var/spool/news/message.id/016/<tfPea.1872$oY6.162833@xxxxxxxxxxxxxxxxxxxxx>)
uk.local.southwest: will fetch 9196 
(/var/spool/news/message.id/231/<dJSea.9$Zd6.6@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>)
Disconnected from news.demon.co.uk.
wrote active file with 37166 lines
Forked child process to update XOVER information.

So, everything fine for demon.service, then fetchnews says it'll fetch a bunch 
of articles in uk.local.southwest, and then it just seems to give up.

Then, I immediately ran fetchnews again, and got 

demon.service: no new articles

followed by exactly the same output from uk.local.southwest, ending with:

uk.local.southwest: will fetch 9196 
(/var/spool/news/message.id/231/<dJSea.9$Zd6.6@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>)
Disconnected from news.demon.co.uk.
wrote active file with 37166 lines
Forked child process to update XOVER information.

I then turned on debugmode.  This is what I got in news.all:

Mar 22 08:01:26 codewave fetchnews[2034]: leafnode 1.9.36.rel: verbosity level 
is 4
Mar 22 08:01:26 codewave fetchnews[2034]: config: debugmode is 1
Mar 22 08:01:26 codewave fetchnews[2034]: config: server is news.demon.co.uk
Mar 22 08:01:26 codewave fetchnews[2034]: config: no LIST NEWSGROUPS for 
news.demon.co.uk
Mar 22 08:01:26 codewave fetchnews[2034]: config: expire is 60 days
Mar 22 08:01:26 codewave fetchnews[2034]: config: initialfetch is 100
Mar 22 08:01:26 codewave fetchnews[2034]: config: crosspostlimit is 4 groups
Mar 22 08:01:26 codewave fetchnews[2034]: config: postings have max. 6000 
lines
Mar 22 08:01:26 codewave fetchnews[2034]: config: postings have max. 100000 
bytes
Mar 22 08:01:26 codewave fetchnews[2034]: config: timeout_long is 14 days
Mar 22 08:01:26 codewave fetchnews[2034]: try_lock(timeout=5), 
fqdn="codewave.demon.co.uk"
Mar 22 08:01:26 codewave fetchnews[2034]: Last LIST done 348680 seconds ago: 
NEWGROUPS 
Mar 22 08:01:27 codewave fetchnews[2034]: <200 news.demon.co.uk InterNetNews 
NNRP server INN 2.4.0 (20030115 CVS prerelease) ready (posting ok).
Mar 22 08:01:27 codewave fetchnews[2034]: connected to 158.152.254.254:119, 
reply: 200
Mar 22 08:01:27 codewave fetchnews[2034]: >MODE READER
Mar 22 08:01:27 codewave fetchnews[2034]: <200 news.demon.co.uk InterNetNews 
NNRP server INN 2.4.0 (20030115 CVS prerelease) ready (posting ok).
Mar 22 08:01:27 codewave fetchnews[2034]: news.demon.co.uk: 0 articles posted
Mar 22 08:01:27 codewave fetchnews[2034]: >DATE
Mar 22 08:01:27 codewave fetchnews[2034]: <111 20030322080120
Mar 22 08:01:27 codewave fetchnews[2034]: check_date: news.demon.co.uk: server 
time 1048320080, our time 1048320087
Mar 22 08:01:27 codewave fetchnews[2034]: >NEWGROUPS 030322 080000 GMT
Mar 22 08:01:27 codewave fetchnews[2034]: <231 New newsgroups follow.
Mar 22 08:01:27 codewave fetchnews[2034]: Reading server info from 
/var/spool/news/leaf.node/news.demon.co.uk
Mar 22 08:01:27 codewave fetchnews[2034]: >GROUP demon.service
Mar 22 08:01:27 codewave fetchnews[2034]: <211 2746 10041 12825 demon.service
Mar 22 08:01:27 codewave fetchnews[2034]: demon.service: no new articles 
Mar 22 08:01:27 codewave fetchnews[2034]: >GROUP uk.local.southwest
Mar 22 08:01:27 codewave fetchnews[2034]: <211 2135 7004 9196 
uk.local.southwest
Mar 22 08:01:27 codewave fetchnews[2034]: uk.local.southwest: considering 
articles 9190 - 9196 
Mar 22 08:01:27 codewave fetchnews[2034]: >XOVER 9190-9196
Mar 22 08:01:28 codewave fetchnews[2034]: <224 9190-9196 fields follow
Mar 22 08:01:28 codewave fetchnews[2034]: >ARTICLE 9190
Mar 22 08:01:28 codewave fetchnews[2034]: >GROUP talk.bizarre
Mar 22 08:01:28 codewave fetchnews[2034]: >GROUP uk.tech.home-automation
Mar 22 08:01:28 codewave fetchnews[2034]: >GROUP uk.jobs.offered
Mar 22 08:01:28 codewave fetchnews[2034]: >GROUP alt.support.diet
Mar 22 08:01:28 codewave fetchnews[2034]: >GROUP alt.autos.saab
Mar 22 08:01:28 codewave fetchnews[2034]: >GROUP alt.fan.jennicam
Mar 22 08:01:28 codewave fetchnews[2034]: >GROUP uk.jobs.contract
Mar 22 08:01:28 codewave fetchnews[2034]: >GROUP comp.windows.x.kde
Mar 22 08:01:28 codewave fetchnews[2034]: >QUIT
Mar 22 08:01:29 codewave fetchnews[2034]: wrote active file with 37166 lines
Mar 22 08:01:29 codewave fetchnews[2035]: Process forked.
Mar 22 08:01:29 codewave fetchnews[2034]: child has process ID 2035
Mar 22 08:01:29 codewave fetchnews[2035]: Process done.

Now, I could understand if it did the same thing every time, but here's the 
weird thing: I then ran it _again_, in exactly the same way, debugmode on, 
with vvvv verbosity, and it worked.  Absolutely fine.  I got articles in all 
the subscribed groups bar one low-traffic one.  93 new articles in total, 
which is what I'd expect.

Any ideas where I go from here?  I can't see what to do next, really.

Thanks,

Matt

-- 
"It's the small gaps between the rain that count,
 and learning how to live amongst them."
	      -- Jeff Noon

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

Follow-Ups:
- Re: [leafnode-list] (Discovery) Problems after upgrade to 1.9.33
  - From: Matt Gibson

References:
- Re: [leafnode-list] Problems after upgrade to 1.9.33
  - From: Matt Gibson

Prev by Date: Re: [leafnode-list] 1.9.33 posting to post.usenet.com
Next by Date: [leafnode-list] Re: leafnode-2 has wrong group counts
Previous by thread: Re: [leafnode-list] Problems after upgrade to 1.9.33
Next by thread: Re: [leafnode-list] (Discovery) Problems after upgrade to 1.9.33
Index(es):
- Date
- Thread