Ubuntu 14.04 headless
Deluge 1.3.11
Libtorrent 0.16.17
About a month ago I noticed deluge would stop all downloading and uploading approximately 2 hours after a restart of the daemon. Starting last night it won't download, even after a forced restart. I love the SW, but ever since the libtorrent issue started causing problems with uploading, it seems to have progressively taken a downhill path. I have disabled the tracker proxy as another post seemed to indicate a bug, and that does get uploading going, though the speed it extremely slow. I've also disabled DHT use per Cas's comment in another post.
I run it through PIA VPN, and use Sock 5 with auth web seed and peer proxys.
Upload and Download Dying After Few Hours
-
- New User
- Posts: 5
- Joined: Sun Mar 08, 2015 10:47 pm
Re: Upload and Download Dying After Few Hours
Try a bridge or a super bridge using IPv6.
Re: Upload and Download Dying After Few Hours
I updated libtorrent to 1.0.3, and that seems to have fixed most of my issues. Seeding is still a bit slow, but otherwise looking good. I'll check it again after running overnight and see if it holds up.
As far as bridging, how would I go about doing it? If the update doesn't fix it I will try that next.
As far as bridging, how would I go about doing it? If the update doesn't fix it I will try that next.
Re: Upload and Download Dying After Few Hours
After 24 hours still seeding without the need to restart. Seeding speed is still well below limit.
I reset all my ltConfig settings to default, and turned on proxy for everything. This is the best performance I've seen in months, along with a few others I'm gonna say upgrading may be a better move than sticking with 0.16.17. At least for my setup it's true.
I reset all my ltConfig settings to default, and turned on proxy for everything. This is the best performance I've seen in months, along with a few others I'm gonna say upgrading may be a better move than sticking with 0.16.17. At least for my setup it's true.
Re: Upload and Download Dying After Few Hours
Maybe your ISP is smelling your data volume in terms of number of connections (not in terms of total volume of data). Maybe your ISP knows to allow "too many" connections to a torrent downloader but not to a torrent library manager? My ISP is an idiot, and uses double-checking software from about 1986 on hardware from about 2004. If you know how to circumvent their stupidity maybe you can look at router settings and port forwarding with something like that kind of stupidity in mind?
Just a thought ... since you seem to concede that reverting to default Lib-Torrent settings has helped the issue a little. If you can bridge with IPv6 you might even throw your ISP a BIGGER curve-ball ... LOL. I bet mine is still struggling with the IP v 2 to v 3 change ...
Just a thought ... since you seem to concede that reverting to default Lib-Torrent settings has helped the issue a little. If you can bridge with IPv6 you might even throw your ISP a BIGGER curve-ball ... LOL. I bet mine is still struggling with the IP v 2 to v 3 change ...
Re: Upload and Download Dying After Few Hours
Everything did die once since the upgrade. Restarted the service, and running fine since then. I have seen higher upload speeds, and have been able to move torrents out of the queue as they reach their share ratio.
I'm sure this is a libtorrent issue as I was unable to seed after upgrading to 0.16.x, and seeding is back with 1.0.3. I wouldn't put stupidity past my ISP though. My connection resets about once a day, and they have failed to fix it after upgrading about every piece of HW from the router to the line in the street. As I run VPN on my seedbox, with Sock5, I don't think they should be too aware of what I'm doing though.
I'm sure this is a libtorrent issue as I was unable to seed after upgrading to 0.16.x, and seeding is back with 1.0.3. I wouldn't put stupidity past my ISP though. My connection resets about once a day, and they have failed to fix it after upgrading about every piece of HW from the router to the line in the street. As I run VPN on my seedbox, with Sock5, I don't think they should be too aware of what I'm doing though.