Deluged Hangs Randomly After Downloading a Torrent

[Monkey]

OS: Ubuntu 11.04 (Completely up to date)
Libtorrent: 0.15.5.0 (Ubuntu Package)
Deluge: 1.3.3 (From PPA)

I've installed "deluged" and "deluge-web" from PPA. A seemingly random amount of time after downloading a Torrent, Deluge stops being able to download/upload.

I add a torrent through the web interface and it grabs the file and starts its work. As it connects to Peers... the number of peers drops down to zero again and then starts over. It seems like it's stuck in a loop of connecting to various peers and then disconnecting from them all. During this time, there's absolutely no transfer of data. If I leave it for a looooong time, sometimes it may start downloading a little but there's no upload at all. If I kill the daemon and start it back up, it immediately starts downloading at a high speed and uploading like normal.

I've actually had this problem ever since Ubuntu 10.10 but I figured it would be a bug that would be fixed. I've tried the versions of Deluge that came with Ubuntu 10.10, 11.04 and PPA with no resolution. So I'm trying to figure out if I'm configuring it wrong or if it's just a long standing, hard to troubleshoot bug.

I've enabled Debug logging and when Deluge does this, there's no errors of any type in the log. Attached are some screen shots of my config, thinking maybe someone has a suggestion. I would have included the Debug log too but I accidentally overwrote it and so I'll include it next time it happens but like I said, I see nothing in there out of the norm. Help would be very much appreciated.

[Cas]

The first thing I would suggest is that you update the libtorrent to 0.15.6 from the PPA.

Have you tried with a clean config and your title says deluged hangs but do you just mean that the torrents dont transfer?

[Monkey]

Yea, I guess Torrent not transferring would be a better description. I have tried with a clean config, same issue comes back immediately. I'll update to the PPA Libtorrent this afternoon and get back to you on how that works, thanks for the suggestion!

[HolgiH]

Hi - this is not going to help much, but I just saw exactly this symptom yesterday on WindowsXP, connected to the daemon on localhost (using the refreshed 1.3.3 with the latest libtorrent). I had to stop the daemon, and even repeated attempts to get the torrent going again failed in the same manner: it found a bunch of peers, established a bunch of connections, then stalled.
I "fixed" the problem by using Azureus to download ~30% of the torrent to the same datafile; afterwards Deluge could pick it up (after a manual recheck) and continued like a champ.
Looks like something gets libtorrent's panties in a bunch.

[Monkey]

Update: I've updated to the version of LibTorrent in the PPA (0.15.6-2~natty) and still the same thing continues. I will provide a debug log here in a day or two.

[Monkey]

Alrighty, attached is a log file from a series of downloads. I've been paying extra attention to how this problem happens. Say I just turned the machine on from scratch, the first Torrent downloads fast and immediately. Afterwords, the following happens:

1. I add Torrent through Web Interface
2. It connects to peers but no seeders, in fact seeders available even lists as zero
3. I never transfer data to the peers I'm connected to, it keeps connecting/disconnecting over and over. I'l be connected to 5, then 50, then 10, then 30, then 0, etc
4. 20-45 minutes later, it gets a full list of Seeders and Peers then starts downloading full speed
5. If I terminate Deluged and start it back up, it will get a full list of Seeders/Peers and start downloading immediately

Additional info about my setup, in case it helps.

-Comcast ISP
-Running on an Intel Atom based system
-Router is running DD-WRT v24-sp2 (08/07/10) with HTB QoS enabled
-I've tried several other Torrent programs and they don't have this problem but I like Deluge the best and thus want to keep using it

If anyone has some suggestions, they'd be more than welcome.

Thanks!

[Monkey]

*bump* Any thoughts? If there's more information I can provide, just let me know. This problem has stumped me.