Subject: Re: Tracker: [Could not parse bencoded data] on reseed attempt - msg#00022

Previous Message by Date: click to view message preview

Re: Tracker: [Could not parse bencoded data] on reseed attempt

On Wed, Jul 09, 2008 at 03:57:55PM -0400, David Willoughby wrote: > This is normally either with a tracker issue or the tracker is down. That > is normally what happens when i see this error. Most of the time that is > when the tracker is up but itsn't responding to the tracker request rtorrent > is sending. It will say something like timeout if the tracker is down > completely. It could be something else but i always see that error when the > tracker host is up but isn't responding to the tracker requests. I am pretty sure the tracker is not down, since I typically have lots of other torrents talking to the same tracker, which is normally www.thetradersden.org. I have seen the tracker go down at times, that's a very different "event signature", all my active torrents complain about not reaching the tracker. Maybe there is something wrong with the tracker, but it's highly suggestive to me that I have very rarely seen the inability to parse bencoded data on first downloading a torrent file but it happens every darn time when I've already successfully downloaded the torrent files! Thanks, - Alan -- Alan S. Rojer rojer@xxxxxxx

Next Message by Date: click to view message preview

Re: Tracker: [Could not parse bencoded data] on reseed attempt

On Wed, Jul 09, 2008 at 10:00:56PM +0200, Josef Drexler wrote: > You can enable the tracker_dump option to record what it actually > sends, and maybe that will provide a clue why it is misbehaving. Ha! My bad: d1:failure reason74:Connection limit exceeded! You should only seed/upload 10 shows at a time.e Funny that I can have lots more than 10 seeds going as long as I never close them. Perhaps in that sense the tracker IS broken! Serves me right for trying to help out a stranded leecher! OK, all cleared up, many thanks! > (It would probably be useful if rtorrent displayed the undecoded > message in case it cannot be decoded, however.) I'll second that, if I'd seen the message I wouldn't have had to waste your precious time! ;-) BTW, is there a simple command-line incantation to "bdecode" a torrent file for the curious? - Alan -- Alan S. Rojer rojer@xxxxxxx

Previous Message by Thread: click to view message preview

Re: Tracker: [Could not parse bencoded data] on reseed attempt

On Wed, Jul 09, 2008 at 03:57:55PM -0400, David Willoughby wrote: > This is normally either with a tracker issue or the tracker is down. That > is normally what happens when i see this error. Most of the time that is > when the tracker is up but itsn't responding to the tracker request rtorrent > is sending. It will say something like timeout if the tracker is down > completely. It could be something else but i always see that error when the > tracker host is up but isn't responding to the tracker requests. I am pretty sure the tracker is not down, since I typically have lots of other torrents talking to the same tracker, which is normally www.thetradersden.org. I have seen the tracker go down at times, that's a very different "event signature", all my active torrents complain about not reaching the tracker. Maybe there is something wrong with the tracker, but it's highly suggestive to me that I have very rarely seen the inability to parse bencoded data on first downloading a torrent file but it happens every darn time when I've already successfully downloaded the torrent files! Thanks, - Alan -- Alan S. Rojer rojer@xxxxxxx

Next Message by Thread: click to view message preview

Re: Tracker: [Could not parse bencoded data] on reseed attempt

On Jul 9, 2008, at 9:39 PM, Alan Rojer wrote: [...] I have one persistent problem, however. On numerous occasions, when I have completed a torrent and closed its files with ^D ^D, then later downloaded the torrent again to reseed, rtorrent reports: Tracker: [Could not parse bencoded data] This indicates that the tracker is sending a garbage reply. It *should* send a bencoded message (even if there was an error), but what it sends cannot be decoded at all. That means the tracker is broken. You can enable the tracker_dump option to record what it actually sends, and maybe that will provide a clue why it is misbehaving. (It would probably be useful if rtorrent displayed the undecoded message in case it cannot be decoded, however.) -- Josef Drexler josef@xxxxxxxxxxxx