Alt.Binz forum
New Alt.Binz versions => Requests => Closed requests => Topic started by: gever on January 24, 2012, 11:08:38 pm
-
When downloading from my provider: news.lightningusenet.com
http://www.nzbindex.nl/release/63371065/Dik-Trom-post-op-www.nzbchronicle.net-0197-DT0717.par2.nzb
I get an endless retry off failing part
From log:
[2012-01-24 23:05:48] [T6] Retry 127/137 Dik Trom post op www.nzbchronicle.net [31/97] - "DT0717.part030.rar" yEnc
[2012-01-24 23:05:48] [T6] StatusCode: 499
[2012-01-24 23:05:48] [T7] Retry 21/137 Dik Trom post op www.nzbchronicle.net [45/97] - "DT0717.part044.rar" yEnc
[2012-01-24 23:05:48] [T7] StatusCode: 499
[2012-01-24 22:56:24] [T7] Retry 85/137 Dik Trom post op www.nzbchronicle.net [53/97] - "DT0717.part052.rar" yEnc
[2012-01-24 22:56:24] [T7] StatusCode: 499
Possible solution is:
right click give an option to stop downloading this part and assembling of the RAR.
The repair function will then solve the broken part
-
Ah, I thought this rang a bell:
https://www.altbinz.net/forum/help-5/status-code-499/
So, I guess the same comment still stands: it would be helpful to know from your provider (or xsnews, which they seem to be reselling) what they've set for 499, and why they're using it.
-
It would be nice if I could ask my provider (reseller) why he is sending 499, and to fix the problem of the 499.
How do you rate my chance in solving the problem at the provider, or with the help of a fantastic programmer which could give us an feature to solve (work around) this problem. Why not end an endless loop simple with manual intervention? Or apply the setting "Connection option" 423, 430, 502 also for 499: try a number of times with delay and stop trying because when it fails it will never be available.
I'm just a simple guy. Probably you address this is a request for a new feature and I posted this in the wrong topic. Is this the way forward or do you have an other suggestion.
-
I'll add 499 to the connection retry list.
-
I just meant it would be useful to know what 499 means for your provider ;) In your position, I'd certainly be curious about the specific reason why my service was failing, and would probably want to post a ticket, but that's obviously separate from anything Rdl implements.
-
I agree with Hecks on this. You should contact your usenet provider about this.
-
499 code added to retry list