Opened 15 years ago
Closed 13 years ago
#430 closed bug (Fixed)
invalid bencoding of tracker response
Reported by: | max@… | Owned by: | andar |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | Core | Version: | 1.2.1 |
Keywords: | Cc: | ipse.reg@… |
Description
[DEBUG ] 14:55:40 alertmanager:97 tracker_error_alert: Gorod.tmy.[HDTV].mkv (http://tracker.0day.kiev.ua/announce.php?passkey=630bd4ffb9c1588f8a32f4792243e5b9) (200) invalid bencoding of tracker response: "0x31 0x4294967179 0x8 0x0 0x0 0x0 0x0 0x0 0x0 0x3 J0x4294967217 0x4294967216 0x4294967242 0x4294967244 +I-*K0x4294967244 0x4294967241 4475I540x4294967218 0x4294967242 0x4294967245 0x4294967244 S@0x21 40x4294967221 *HM-*60x4294967216 JM0x4294967189 0x4294967279 0x4294967270 `0x0 0x3 ff0x6 0x24 0x0 0x0 0x0 0x0 0x4294967295 0x4294967295 0x3 0x0 e0x4294967267 0x29 0x4294967279 E0x0 0x0 0x0 " (2)
seems that response is cyrillic
Change History (25)
comment:1 Changed 15 years ago by anonymous
comment:2 Changed 15 years ago by oscar
Also getting this, with RC8.
[DEBUG ] 23:55:11 alertmanager:97 tracker_error_alert: xxx (http://xxx.xxx/announce.php?passkey=xxx) (200) invalid bencoding of tracker response: "0x31 0x4294967179 0x8 0x0 0x0 0x0 0x0 0x0 0x0 0x3 0x28 0x4294967244 0x4294967233 0x9 0x4294967235 00x12 0x5 0x4294967248 U0x4294967294 0x0 %0x4294967206 Ph0x4294967281 0x4294967217 ]0x4294967200 +(0x4294967222 0x28 0x27 0x4294967172 e$e0x4294967295 0x4294967190 0x4294967196 0x31 0x4294967228 z0x127 0x4294967268 FCNc0x24 0x4294967187 0x4294967275 |=0x4294967283 0x4294967195 0x4294967270 0x4294967268 0x4294967178 0x4294967183 0x12 0x4294967198 q0x4294967235 W0x4294967294 0x4294967232 840x20 =b0x4294967269 0x4294967188 z0x4294967261 G0x4294967288 0x4294967206 v$;0x4294967173 }[}0x4294967201 0x4294967209 0x4294967169 0x4294967235 0x3 0x4294967258 @0x4294967205 0x4294967280 0x10 0x4294967258 0x4294967173 Q0x4294967214 0x4294967240 0x4294967289 0x7 0x0 0x0 0x4294967295 0x4294967295 0x3 0x0 0x4294967184 S0x4294967212 Nm0x0 0x0 0x0 " (3)
comment:3 Changed 15 years ago by anonymous
- Component changed from 0.5.x to core
- Milestone set to 1.0.0
- Owner changed from markybob to andar
- Priority changed from major to critical
- Version changed from 0.9.05 (1.0.0_RC5) to 0.9.08 (1.0.0_RC8)
comment:4 Changed 15 years ago by anonymous
I also get this error on every tracker.
comment:5 Changed 15 years ago by oscar
My guess is that this tracker tries to tell me that this version of Deluge is not allowed, they are rather strict. Other trackers I've tested works just fine.
comment:6 Changed 15 years ago by anonymous
- Version changed from 0.9.08 (1.0.0_RC8) to 0.9.09 (1.0.0_RC9)
I get the same error! but some files downloading...
comment:7 Changed 15 years ago by anonymous
- Version changed from 0.9.09 (1.0.0_RC9) to 1.0.0
I also get this error on FL Other trackers (like TL and TB) give no problemms at all...
comment:8 Changed 15 years ago by anonymous
Confirmed on FL, was working until I updated Deluge :(
comment:9 Changed 15 years ago by storm_sw@…
same error in 1.0.0
comment:10 Changed 15 years ago by anonymous
+1 on Deluge 1.0, however NOT on all trackers
comment:11 Changed 15 years ago by anonymous
Error: (200) invalid bencoding of tracker response - received when trying to announce on http://zamunda.net
comment:12 Changed 15 years ago by anonymous
In 1.0.2 bug is not found. Downloads are now excellent for those trackers which was a mistake
comment:13 Changed 15 years ago by andar
- Resolution set to fixed
- Status changed from new to closed
Fixed.
comment:14 Changed 15 years ago by anonymous
- Resolution fixed deleted
- Status changed from closed to reopened
When I pause torrents on tracker torrents.ru, deluge-1.0.4 says me alertmanager:101 tracker_error_alert: Emperor-7Wolf (http://bt.torrents.ru/announce.php?uk=) (200) invalid bencoding of tracker response: "" (1) alertmanager:101 tracker_error_alert: Summoner (http://bt.torrents.ru/announce.php?uk=) (200) invalid bencoding of tracker response: "" (1)
comment:15 Changed 15 years ago by nicklas.haraldsson@…
- Milestone changed from 1.0.0 to 1.0.5
Have the same problem in 1.0.5 from one of my trackers
comment:16 Changed 14 years ago by markybob
- Resolution set to fixed
- Status changed from reopened to closed
been fixed a little while back
comment:17 Changed 14 years ago by cheMIST
- Milestone changed from 1.0.5 to 1.1.0
- Resolution fixed deleted
- Status changed from closed to reopened
- Version changed from 1.0.0 to 1.1.0_RC1
Have the same problem in 1.0.7 and 1.1.0_RC1
comment:18 Changed 14 years ago by markybob
- Resolution set to fixed
- Status changed from reopened to closed
then use a tracker that isnt retarded. this isnt our problem
comment:19 Changed 14 years ago by ipse
- Cc ipse.reg@… added
- Resolution fixed deleted
- Status changed from closed to reopened
- Version changed from 1.1.0_RC1 to 1.1.0
I've just installed Deluge 1.1.0 on Ubuntu 8.10 x86_6. After downloading few torrents they've started seeding and I see following error in two of them (with Queued status):
torrents.ru: Ошибка: invalid bencoding of tracker response: ""
comment:21 Changed 14 years ago by civmaniac@…
I get this message on some torrents when I start deluge. It disappears after a while. Deluge 1.1.7, Ubuntu 9.04
comment:22 Changed 14 years ago by while
- Version changed from 1.1.0 to 1.1.6
xtremebg.com: Грешка: invalid bencoding of tracker response: ""
Deluge 1.1.6 on Ubuntu 9.04 (x86)
comment:23 Changed 13 years ago by andar
- Resolution set to fixed
- Status changed from reopened to closed
There was a bug in an older version of libtorrent that could cause this. Please upgrade to the latest version, 0.14.7.
comment:24 Changed 13 years ago by simonbcn
- Resolution fixed deleted
- Status changed from closed to reopened
- Version changed from 1.1.6 to 1.2.1
Same problem in Deluge 1.2.1
xxx.org: Error: invalid bencoding of tracker response: ""
comment:25 Changed 13 years ago by andar
- Resolution set to fixed
- Status changed from reopened to closed
The tracker responded with nothing so it's an invalid bencoded response.
I get the same error!