Bug#572367: rtorrent: Unsnubbing doesn't seem to work
forwarded 572367 https://github.com/rakshasa/rtorrent/issues/37 thanks sacrificial-spam-addr...@horizon.com wrote: Could you please try version 0.8.9 in wheezy and see if this bug is still present? As of Version: 0.8.9-2 with libtorrent14 Version: 0.12.9-3 it's still there. (I'm running sid rather than wheezy; I figure for this purpose that's not a problem.) 4 peers, each receiving 20 k/s, were snubbed for a second, then immediately unsnubbed, and their rates have gone to 0 and stayed there. If I kick them off, they reconnect and start transferring again. Thanks a lot for checking this. I've forwarded it upstream, let's see what they say. Cheers, -- Benoît Knecht -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572367: rtorrent: Unsnubbing doesn't seem to work
Benoît Knecht wrote: sacrificial-spam-addr...@horizon.com wrote: Could you please try version 0.8.9 in wheezy and see if this bug is still present? As of Version: 0.8.9-2 with libtorrent14 Version: 0.12.9-3 it's still there. (I'm running sid rather than wheezy; I figure for this purpose that's not a problem.) 4 peers, each receiving 20 k/s, were snubbed for a second, then immediately unsnubbed, and their rates have gone to 0 and stayed there. If I kick them off, they reconnect and start transferring again. Thanks a lot for checking this. I've forwarded it upstream, let's see what they say. In case you're not following the upstream ticket: Would you be able to build libtorrent [1] and rtorrent [2] from source, in their latest revision from github, and see if the issue is still there? [1] git://github.com/rakshasa/libtorrent.git [2] git://github.com/rakshasa/rtorrent.git Cheers, -- Benoît Knecht -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572367: rtorrent: Unsnubbing doesn't seem to work
In case you're not following the upstream ticket: I'm not; I don't even know where their bug tracker is. Would you be able to build libtorrent [1] and rtorrent [2] from source, in their latest revision from github, and see if the issue is still there? Done. Exact git commits are libtorrent ff60f659e3270b995c1df7cec991aec43b62b29f rtorrent d25c4b25aec09d19ae10941f7e22b97b00a94bfc I've only let the connection sit choked for 5 minutes or so, but here: IP UP DOWN PEER CT/RE/LO QSDONE REQ SNUB FAILED * 78.180.99.43 0.00.075.1 r /cn/ci 0/016 uTorrent 3.0.0.0 203.161.79.192 0.00.0163.8 r /Cn/cn 0/0 100 uTorrent 1.8.5.0 24.142.56.27 0.00.0163.8 r /Cn/cn 0/0 100 uTorrent 1.8.5.0 68.60.53.4 0.00.0163.8 r /Cn/cn 0/0 100 uTorrent 1.8.5.0 95.34.190.1850.00.0163.8 r /Cn/cn 0/0 100 uTorrent 3.1.2.0 68.231.118.970.00.0163.8 r /cn/ci 0/0 100 uTorrent 3.0.0.0 14.201.139.177 0.00.0163.8 r /Cn/cn 0/0 100 uTorrent 3.0.0.0 71.127.1.172 0.00.00.0R /Cn/cn 0/098 uTorrent 3.1.2.0 80.202.31.1470.00.00.0R /Cn/cn 0/0 100 uTorrent 2.2.0.0 109.224.133.220 0.00.0163.8 r /Cn/cn 0/0 100 uTorrent 3.1.2.0 68.114.141.450.00.0163.8 r /Cn/cn 0/0 100 uTorrent 1.8.2.0 That first peer was receiving data at a good clip before I briefly choked it with *. If I kick, it'll reconnect in a few seconds and start downloading... * 78.180.99.43 11.8 0.068.3 r /ci/ui 13/0 16 uTorrent 3.0.0.0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572367: rtorrent: Unsnubbing doesn't seem to work
sacrificial-spam-addr...@horizon.com wrote: In case you're not following the upstream ticket: I'm not; I don't even know where their bug tracker is. Oh sorry, the link was in a previous mail; here it is again, if you're interested: https://github.com/rakshasa/rtorrent/issues/37 Would you be able to build libtorrent [1] and rtorrent [2] from source, in their latest revision from github, and see if the issue is still there? Done. Exact git commits are libtorrent ff60f659e3270b995c1df7cec991aec43b62b29f rtorrent d25c4b25aec09d19ae10941f7e22b97b00a94bfc I've only let the connection sit choked for 5 minutes or so, but here: IP UP DOWN PEER CT/RE/LO QSDONE REQ SNUB FAILED * 78.180.99.43 0.00.075.1 r /cn/ci 0/016 uTorrent 3.0.0.0 203.161.79.192 0.00.0163.8 r /Cn/cn 0/0 100 uTorrent 1.8.5.0 24.142.56.27 0.00.0163.8 r /Cn/cn 0/0 100 uTorrent 1.8.5.0 68.60.53.4 0.00.0163.8 r /Cn/cn 0/0 100 uTorrent 1.8.5.0 95.34.190.1850.00.0163.8 r /Cn/cn 0/0 100 uTorrent 3.1.2.0 68.231.118.970.00.0163.8 r /cn/ci 0/0 100 uTorrent 3.0.0.0 14.201.139.177 0.00.0163.8 r /Cn/cn 0/0 100 uTorrent 3.0.0.0 71.127.1.172 0.00.00.0R /Cn/cn 0/098 uTorrent 3.1.2.0 80.202.31.1470.00.00.0R /Cn/cn 0/0 100 uTorrent 2.2.0.0 109.224.133.220 0.00.0163.8 r /Cn/cn 0/0 100 uTorrent 3.1.2.0 68.114.141.450.00.0163.8 r /Cn/cn 0/0 100 uTorrent 1.8.2.0 That first peer was receiving data at a good clip before I briefly choked it with *. If I kick, it'll reconnect in a few seconds and start downloading... * 78.180.99.43 11.8 0.068.3 r /ci/ui 13/0 16 uTorrent 3.0.0.0 Wow, that was fast! Thanks again for your great feedback, I'll let upstream know. Cheers, -- Benoît Knecht -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572367: rtorrent: Unsnubbing doesn't seem to work
tags 572367 moreinfo thanks Hi, sacrificial-spam-addr...@horizon.com wrote: Toggling peer snubbing off with * seems to leave that peer permanently choked, even when it wakes up and starts feeding me data. The only way I can find to bring the connection back to life is to kick off the peer and let it reconnect. Could you please try version 0.8.9 in wheezy and see if this bug is still present? Cheers, -- Benoît Knecht -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
