Problem with trn and NNTPSwitch front-end
Status: Beta
Brought to you by:
wayned
|
From: Patrick V. <pat...@pe...> - 2010-09-06 14:13:35
|
Hi there, I recently switched to a new ISP, and also got a new newsserver that way. It's implemented using NNTPSwitch, and I've had some trn-related problems with that before. It seems trn barfs very badly when the connection idles out, and just plain quits. I also tested this using test77, and same behavior. Some relevant logging: Entering alt.binaries.hdtv.x264:>GROUP alt.binaries.hdtv.x264 <211 9541364 715431938 727600411 alt.binaries.hdtv.x264 >LIST active alt.binaries.hdtv.x264 <215 Active file follows <alt.binaries.hdtv.x264 0726788781 0720289612 y >XOVER 725893909-725894228 <224 725893909-725894228 fields follow <400 news.xs4all.nl: Idle timeout. >QUIT <400 dreader17.news.xs4all.nl: Idle timeout. >QUIT <205 Timeout after 30 seconds, articles 0, bytes 0, groups 0, posts 0, postbytes 0 a+ [23;1H >HEAD 725893913 <205 Timeout after 30 seconds, articles 0, bytes 0, groups 1, posts 0, postbytes 0 [H[J >BODY 725893913 <503 Server closed connection. >QUIT <503 Server closed connection. Explanation in words: I enter a.b.hdtv.x264, get the overviews and the article overview is presented. Then I jus wait about 5 or 10 minutes. Then, when I press 'a' to select the first article, I get the two 400 and the single 205 messages. Strangely enough, these are from previous (I have 4 newsservers defined in my .trn/access file). Then, when I press enter, I see the HEAD command being performed, the 503's are echoed, and then trn just silently quits, undoing all the xover-effort performed before. Shouldn't it be doing a bit more effort to re-open the connection, to just continue where it left of? It should know all info needed to re-open the connection, and continue on...? The server where this happens is: $ telnet news.ziggo.nl 119 Trying 212.54.40.12... Connected to news.ziggo.nl. Escape character is '^]'. 200 cache1 NNTPSwitch-1.00-ziggo-v1, 68388 groups available, posting allowed, slot 71, connections 1 Be aware this needs a login to be used. Regards, Patrick. |