since updating I am getting this error "Connection error " This tracker does not support multiple hash scrapes per request"
I can't for the life of me find a setting that will keep me from getting this error.
Any help appreciated.
In general that isn't an error, it is just saying that Vuze has to make separate 'scrape' requests to the tracker, per torrent, to get the current seed/peer counts. If you look in the 'Sources' tab for one of the torrents with this message then hopefully you will be able to see seed/peer counts for the tracker.
Not sure how this could be related to the update though.
(09-02-2014, 07:28 PM)'parg' Wrote: [ -> ]In general that isn't an error, it is just saying that Vuze has to make separate 'scrape' requests to the tracker, per torrent, to get the current seed/peer counts. If you look in the 'Sources' tab for one of the torrents with this message then hopefully you will be able to see seed/peer counts for the tracker.
Not sure how this could be related to the update though.
Thanks for your reply, under tracker status it says "Connection Error (network not enabled for url "........) then lists the tracker url/ This is odd, i cannot connect to any seeds/peers and have never seen this until the update.
(09-02-2014, 08:22 PM)'sledbc' Wrote: [ -> ] (09-02-2014, 07:28 PM)'parg' Wrote: [ -> ]In general that isn't an error, it is just saying that Vuze has to make separate 'scrape' requests to the tracker, per torrent, to get the current seed/peer counts. If you look in the 'Sources' tab for one of the torrents with this message then hopefully you will be able to see seed/peer counts for the tracker.
Not sure how this could be related to the update though.
Thanks for your reply, under tracker status it says "Connection Error (network not enabled for url "........) then lists the tracker url/ This is odd, i cannot connect to any seeds/peers and have never seen this until the update.
also to note, anything i've downloaded from the same tracker and is complete will seed but nothing new will connect, so its not the tracker.
Are you actually passing data on the seeding torrents? Or are you just not seeing an error for the seeding torrents?
If you are not actually passing data it still could be a tracker specific problem.