Page 1 of 1

Why disconnect on a 430?

PostPosted: Fri Feb 21, 2014 10:38 pm
by Questar_99
Doesn't this put a ton of load on servers if entire posts are missing and failing over to a lower priority server?

Re: Why disconnect on a 430?

PostPosted: Fri Feb 21, 2014 11:07 pm
by Quade
What version are you using? I see no indication it's disconnecting for 430's.

I run it in a special test mode that simulates a 430 on every 4 chunks. The source port hasn't changed meaning it's using the same connection over and over.

If you're talking about Astraweb and random disconnects. That seem to be just an AW issue. It's the only server I see this happen on. Newsbin just reconnects and keeps going.

Re: Why disconnect on a 430?

PostPosted: Sat Feb 22, 2014 12:16 am
by Questar_99
Hi Quade,

I'm running 6.50.3126. Server tab clearly shows a disconnect and then reconnect on a 430. Definitely happens on Easynews, haven't really checked if it happens on any other providers.

Re: Why disconnect on a 430?

PostPosted: Sat Feb 22, 2014 1:08 am
by Quade
How many connections are you allowed to use and how many are you using?

How fast is your connection to the internet?

I tested a file set with a couple thousand chunks, 1 connection and a chunk download failure every 4 chunks and it didn't disconnect.

Then I generated an NZB and damaged at least one chunk per file and downloaded it.

Start: TCP 192.168.10.153:52938 216.196.97.131:563 ESTABLISHED InHost

[22:55:11] HIGH Failed to retrieve Article from Server:news.giganews.com ARTICLE <53080b07$0$44444412620$c3e8da3$69010069@news.astraweb.com>
| 430 no such article
[22:55:59] HIGH Failed to retrieve Article from Server:news.giganews.com ARTICLE <5308033333b0f$0$12620$c3e8da3$69010069@news.astraweb.com>
| 430 no such article
[22:56:35] HIGH Failed to retrieve Article from Server:news.giganews.com ARTICLE <5308333330b14$0$18919$c3e8da3$cc4fe22d@news.astraweb.com>
| 430 no such article
[22:57:19] HIGH Failed to retrieve Article from Server:news.giganews.com ARTICLE <53080b1a$03333$12620$c3e8da3$69010069@news.astraweb.com>
| 430 no such article
[22:57:59] HIGH Failed to retrieve Article from Server:news.giganews.com ARTICLE <53080b20$0$106633331$c3e8da3$33881b6a@news.astraweb.com>
| 430 no such article
[22:58:28] HIGH Failed to retrieve Article from Server:news.giganews.com ARTICLE <53080b24$0$18947$c3e8333da3$cc4fe22d@news.astraweb.com>
| 430 no such article
[22:58:32] HIGH Failed to retrieve Article from Server:news.giganews.com ARTICLE <53080b24$0$18915$c3e8da3$3333cc4fe22d@news.astraweb.com>
| 430 no such article
[22:59:06] HIGH Failed to retrieve Article from Server:news.giganews.com ARTICLE <53080b07$0$44444412620$c3e8da3$69010069@news.astraweb.com>
| 430 no such article
[22:59:07] HIGH Failed to retrieve Article from Server:news.giganews.com ARTICLE <5308033333b0f$0$12620$c3e8da3$69010069@news.astraweb.com>
| 430 no such article


Stop: TCP 192.168.10.153:52938 216.196.97.131:563 ESTABLISHED InHost

And this is what it was when I was done, after 400 megs of download, 2 retries, par downloads and repair. Clearly it's the same connection it was when I started.

So, I can confidently say that Newsbin 6.51RC2 processing 430 errors doesn't disconnect. I'm skeptical that 6.50 is any different since the code is the same. I'd be more inclined to believe that your virus scanner or firewall is messing up the connection and it's mistakenly disconnecting on a 430. Either that or there's something funny with the server I'm not seeing on either Astra or Giganews (I tested on both).

The next step is probably to try 6.51RC2 since it's the one I was just testing with.


And just to be thorough I did the same test with 5 connections

Start:
TCP 192.168.10.153:52951 216.196.97.131:563 ESTABLISHED InHost
TCP 192.168.10.153:52952 216.196.97.131:563 ESTABLISHED InHost
TCP 192.168.10.153:52953 216.196.97.131:563 ESTABLISHED InHost
TCP 192.168.10.153:52954 216.196.97.131:563 ESTABLISHED InHost
TCP 192.168.10.153:52955 216.196.97.131:563 ESTABLISHED InHost


End:
TCP 192.168.10.153:52951 216.196.97.131:563 ESTABLISHED InHost
TCP 192.168.10.153:52952 216.196.97.131:563 ESTABLISHED InHost
TCP 192.168.10.153:52953 216.196.97.131:563 ESTABLISHED InHost
TCP 192.168.10.153:52954 216.196.97.131:563 ESTABLISHED InHost
TCP 192.168.10.153:52955 216.196.97.131:563 ESTABLISHED InHost