snowyu / libtorrent

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

libtorrent connects to seed and idles at 0% #655

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. libtorrent is running on some .fr OVH dedicated server.
2. Uploader uploads a torrent and starts seeding.
3. libtorrent box connects to the seed and does not download, but idles at 0%.
4. While any other leechers connect and download just fine.
5. Seeder has 100mbit line with all ports open and no firewall.
6. libtorrent appearently starts leeching when there's at least 20 leechers or 
after like 20 minutes of idling, cannot reproduce the actual reason, but it 
actual starts downloading after some time pass.
7. Now this is the best part. While it idles connected to the seeder, it actual 
downloads from other leechers.

What is the expected output? What do you see instead?
So if it connects to seeder why doesn't it download immediately, but wait for 
20 minutes of idle?

What version of the product are you using? On what operating system?\
0.12.9

Please provide any additional information below.
Imma go wash my hair now.

Original issue reported on code.google.com by rhazor...@gmail.com on 3 Aug 2014 at 6:59

GoogleCodeExporter commented 9 years ago
the version you specify is suspicious. It looks like an rtorrent version 
number. This is the libtorrent.org (or libtorrent-rasterbar) project. It's not 
related to rtorrent.

Original comment by arvid.no...@gmail.com on 3 Aug 2014 at 8:51

GoogleCodeExporter commented 9 years ago
So why does it say libTorrent 0,12,9 via uTorrent's interface?

Original comment by rhazor...@gmail.com on 3 Aug 2014 at 8:52

GoogleCodeExporter commented 9 years ago
you should ask the rtorrent developers.

Original comment by arvid.no...@gmail.com on 3 Aug 2014 at 5:51

GoogleCodeExporter commented 9 years ago
what's the command line you run btw, on the "libtorrent box"?

Original comment by arvid.no...@gmail.com on 3 Aug 2014 at 5:52

GoogleCodeExporter commented 9 years ago
Updating to 0,13,4 solved the problem.

Original comment by rhazor...@gmail.com on 3 Aug 2014 at 6:15