snowyu / libtorrent

Automatically exported from code.google.com/p/libtorrent
Other
1 stars 0 forks source link

Seed-Peer wrong #228

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
With version 0.15.6 of the seed-peer count is wrong. The tracker returns a 
value very different from the deluge, and often the seed count is always 0, 
even if the tracker marks a much greater number.

Tracker: [img]http://i55.tinypic.com/15frjur.jpg[/img]

Libtorrent 0.15.6: [img]http://i51.tinypic.com/2r544zm.jpg[/img]

The same thing happens with all the other torrent.

Original issue reported on code.google.com by tonibon...@gmail.com on 1 Aug 2011 at 9:07

GoogleCodeExporter commented 9 years ago
the values from the screenshot, are those torrent_status::list_peers/list_seeds 
or torrent_status::complete/incomplete?

The code is very straightforward, it sounds like you assume those numbers being 
displayed are complete/incomplete, you might want to make sure that's the case. 
Another good way to figure out what's going on is to get a wireshark dump 
capturing an announce or scrape of the tracker.

Another thing to keep in mind, if there are multiple trackers on a torrent, the 
last one to be scraped or announced to is the one determining what values show 
up.

Original comment by arvid.no...@gmail.com on 18 Sep 2011 at 1:07

GoogleCodeExporter commented 9 years ago
i have same problem and can add:
torrent client(deluge) never deletes peers, eg. i download torrent, i get info 
that there is 100 seeds and 100leechers, ok deluge shows that there is 100 
seeders, later 90 seeders run away and in server there is only 10 seeders, but 
deluge still shows that there is 100 seeders. i use private trackers so there 
is always only one announce url and i don't use DHT or peer exchange.

Original comment by Gymka....@gmail.com on 20 Sep 2011 at 11:13

GoogleCodeExporter commented 9 years ago
example with wireshark:
wireshark message(important 
part)="d8:completei98e10:incompletei0e8:intervali3582e5:peers0:6:peers60:e"
deluge shows="seeds: 0, peers 90"
but as i understood from bittorrent traffic message it should show "seeds: 98, 
peers: 98"
on server="seeds: 97, leeches: 0"(site updates later, on torrent tracker there 
is always delay, so it shows 97 and not 98) 

Original comment by Gymka....@gmail.com on 20 Sep 2011 at 11:43

GoogleCodeExporter commented 9 years ago
wireshark: d8:completei4e10:incompletei0e8:intervali1800e12:min 
intervali30e5:peers0:e
server(not same as in previous post): seeds: 4 leech: 0
deluge: seeds: 0 peers: 0
you can wait all day, update 100 time and nothing changes.

Original comment by Gymka....@gmail.com on 20 Sep 2011 at 12:02

GoogleCodeExporter commented 9 years ago
Arvid in Deluge 1.3.3 I changed the stats displayed to 
torrent_status::list_peers/list_seeds from torrent_status::complete/incomplete 
as a fix for this ticket http://dev.deluge-torrent.org/ticket/1338. I now 
wonder if that ticket was highlighting an issue with libtorrent after all. 

Original comment by caluml...@gmail.com on 20 Sep 2011 at 12:17

GoogleCodeExporter commented 9 years ago
did that change fix that issue? If it did, it seems like it would "fix" it by 
showing some other information that changes more often, and since it's changing 
people don't bother checking to see if it matches what they expect to be there.

Original comment by arvid.no...@gmail.com on 20 Sep 2011 at 7:37

GoogleCodeExporter commented 9 years ago
in deluge 1.3.2 seeds appears like on server, so definetely it was wrong bug fix

Original comment by Gymka....@gmail.com on 21 Sep 2011 at 8:49

GoogleCodeExporter commented 9 years ago
@Arvid I recall that I thought list_peers/list_seeds would also be a better 
representation of the torrents stats so that it would include DHT but I meant 
to ask for clarification from yourself. 

@Gymka that doesn't actually solve it as we simply return to the original issue 
that was reported in the forum which was with complete/incomplete stats display.

Original comment by caluml...@gmail.com on 21 Sep 2011 at 2:06

GoogleCodeExporter commented 9 years ago
I've update to Libtorrent 0.15.8 but the tracker returns a value very different 
from the deluge, and often the seed count is always 0.

Look the same torrent:
Deluge --> http://i55.tinypic.com/2hritl1.jpg
Tracker --> http://i54.tinypic.com/2vtnynr.jpg

Original comment by tonibon...@gmail.com on 11 Oct 2011 at 11:54

GoogleCodeExporter commented 9 years ago
@toniboni 

Could you revert the Deluge change I made and see what the values are with 
0.15.8

http://git.deluge-torrent.org/deluge/commit/?h=1.3-stable&id=1a9ae62669

Original comment by caluml...@gmail.com on 11 Oct 2011 at 12:10

GoogleCodeExporter commented 9 years ago
This still appears to be a bug in Deluge and/or libtorrent -- versions:

Client: 1.3.11
Server: 1.3.10

libtorrent: 0.16.18.0

Original comment by ling...@gmail.com on 3 Apr 2015 at 4:51