Deluge Forum

It has been few months since I notice sometimes downloads will stall. This usually happen to torrents that has been downloading for a long time...probably more than 5 days.

I started noticing this when one of the torrent I tried to download keep on staying at certain percentage. Let's say 60.5%. When I check at the downloads, I can see it saying downloading at 3k/s or 10k/s and fluctuates a lot. But usually at very low speed. So I thought speed is not good for that torrent and let it be. However, after like few days, it still hover around 60.5%...maybe this time at 61.2% and so on. Then I spent some time monitoring this...actually few hours and I can see something is downloading but suddenly the percentage drops. Like for eg, it was at 61.5% then suddenly becomes 60.5%. So I felt something is not right and ran "force check". After running force check, even worst. It fell to maybe 10.5%. Horrible that I lost 50% of downloads that I waited like weeks. So I restarted Deluge daemon and then force check this torrent again. Now this time it checked and showed I have downloaded 91.2%. And eventually the download started moving at good pace and completed the download. Then I checked the files downloaded and it all is in good condition.

Summary:
1) downloads seems stuck at certain percentage but torrent have healthy seeders
2) force check and percentage dropped drastically
3) restart deluge daemon
4) force check again and percentage recovered and become more than before this
5) downloads not stuck anymore and torrent eventually complete
6) check files and all is fine

Any idea? This a known bug or ???

BTW, I only uses webui for torrent management. Deluge is self compiled 1.3.4. Ubuntu 10.04.

Sounds like: http://code.google.com/p/libtorrent/iss ... ail?id=283

yes..very similar to this reported case. Glad that I am not the only one getting this problem. So this is a wide spread problem.

The link provided is posted on libtorrent support. However, those reporting this problem seems to be users of deluge only. As such, can we consider this problem to be deluge only? Or this is libtorrent's fault? Not trying to blame anyone but want to isolate and narrow down the problem.

That's because I created the ticket and pointed Deluge users there to help debug it because it is definitely a libtorrent issue.

i see..thanks for the reply. At least I know this is libtorrent's issue. Will wait for them to fix it.

Devs can't reproduce it and none of us users seem to be able to compile a dev build...

The only FIX seems to be to force a restart of deluge, I have set a nightly cron job for this.