I know I have looking at an old thread but I do not see a "event logging plugin" also when enabling debug logging on the daemon I did not see any hash fails...

http://dev.deluge-torrent.org/ticket/2013
Still a problem for any manual download I make, I largely use flexget but still....

Any chance of a python 2.7 egg getting posted?

Lazybones this is a libtorrent issue: http://code.google.com/p/libtorrent/issues/detail?id=283 Yes, however I doubt a fix will be prompt on this one, as it it currently deemed random. Would it be possible for deluge to pause torrents that have over downloaded by a ratio? Simple fact is that a torre...

Today I had this happen to three torrents all at once.. All where torrents less than 400MB stuck in various % complete with between 1.2 to 2.9GB downloaded. At this rate I will burn through my ISP cap on garbage data alone.

Running 1.3.3 with libtorrent 0.15.9.0 on debian. I have a 699.6 MiB torrent that got stuck at 30% with 1.3GiB download... I forced recheck and it has started over from 0%!

Not everyone is on an unlimited download plan, on larger torrents this can be devastating to monthly caps!

More than a single inbound port seems odd for a torrent client, also if I read the libtorrent API correctly it only binds to one inbound port out of the range anyway. I might open it up to two ports to reduce the chance of binding failure. It only uses one port at a time but if you restart Deluge a...

I think using a single port is the issue, you are best to use a range of ports, say 10 or so. Plus, as mentioned in faq , you are best to use the ports numbers in the range of 49152 to 65535. More than a single inbound port seems odd for a torrent client, also if I read the libtorrent API correctly...

Inbound 3390
Out is now random

Notice it had lost its ports again after a recent set of reboots, I set the outbound ports to random with no luck.. I had to toggle the inbound port to random, wait then toggle it back to my selected port before it would go back.