linuxserver.io

[Support] Linuxserver.io - Deluge

245 posts in this topic Last Reply

Recommended Posts

Anyone else have this issue, deluge totally ignores download limits.

Share this post


Link to post

What I could find, the issue with bandwidth limits is caused by a bugged  libtorrent library (v 1.1.5). Linuxserver.io rebased the image to Alpine Edge that pulls that version which doesn't work with Deluge 1.3.15

 

  • Upvote 1

Share this post


Link to post
What I could find, the issue with bandwidth limits is caused by a bugged  libtorrent library (v 1.1.5). Linuxserver.io rebased the image to Alpine Edge that pulls that version which doesn't work with Deluge 1.3.15
 
Got some links to that please?

Share this post


Link to post

Just installed Deluge,

It doesn't start any Download

Share this post


Link to post
On 5/16/2018 at 7:56 AM, CHBMB said:
On 5/15/2018 at 6:08 PM, cferrero said:
What I could find, the issue with bandwidth limits is caused by a bugged  libtorrent library (v 1.1.5). Linuxserver.io rebased the image to Alpine Edge that pulls that version which doesn't work with Deluge 1.3.15
 

Got some links to that please?

 

sadly no, I was searching about the bandwidth issue (ignoring limits) and what I could find was several coments about being a libtorrent library issue, then I found that comment about the rebase (I can't remember where but was just that line), I checked the update logs and tested the previous build and other based on archlinux, both obey the global limit BUT then I found that something is still off with the upload limit, let's say my line's upload is 20+ Mb/s and I set the global limit on 5, and there are 4 torrents seeding, the individual upload of each torrent will be pretty random each few seconds, ranging between 0 and a few hundreds but the total (0-2 Mb/s) pretty far from the limit (5 Mb).

If I remove the limit, the upload will go 15+++ Mb/s fast.  If put a limit by torrent (1 Mb/s), I can see the upload of each one close to that limit, 800-900 Kb/s. Right now I have the latest version (linuxserver) with individual limit.

Share this post


Link to post

What's the usual memory usage by the this docker image for you guys?

for me, it is over 1GB, even when i'm not running anything.

seed a few shows for a few days, I delete them, but the docker is still at well over 1 gig of usage (docker stats command)

is this normal?

shouldn't the usage go down after a while?

 

thanks!

Share this post


Link to post

Having the same issue discussed above where the global bandwidth limiter isn't doing anything at all. It does work on a per torrent basis, however. 

Share this post


Link to post
On 5/16/2018 at 1:56 PM, CHBMB said:
On 5/16/2018 at 12:08 AM, cferrero said:
What I could find, the issue with bandwidth limits is caused by a bugged  libtorrent library (v 1.1.5). Linuxserver.io rebased the image to Alpine Edge that pulls that version which doesn't work with Deluge 1.3.15
 

Got some links to that please?

doing some general googling I found these links of others in the deluge world with similar issues. Hope this helps

 

https://github.com/arvidn/libtorrent/issues/2857

 

https://dev.deluge-torrent.org/ticket/3153

 

https://forum.deluge-torrent.org/viewtopic.php?p=227823

 

if this is unclear, please forgive my noobish research.

 

 

 

 

Share this post


Link to post

Is anyone else having an issue where once a torrent finishes downloading, it stays in the downloading state @ 100%? The only way to get it to move to seeding is to force a recheck on the file. 

Any idea's what could cause it or a solution to fixing it?

Share this post


Link to post

I'm hoping someone has a fix for this.  Whenever I restart the docker, several of my torrents will have Errors requiring rechecking. It's very annoying as it can take a day or two if it's a very large torrent. 

 

Does anyone else have this problem?

 

Here are my mappings - appdata is set to R/W Slave on an UD.   Thanks in advance for any help

 

1114109374_FireShotCapture133-Highlander_UpdateContainer_-https___1d087a25aac48109ee9a15217a.thumb.png.368298e22dd121f450b9e20fa25ff687.png

 

screenshot.9.thumb.jpg.a9f59f8335b1ff7e3ae752b4e6cf66b1.jpg

Share this post


Link to post
I'm hoping someone has a fix for this.  Whenever I restart the docker, several of my torrents will have Errors requiring rechecking. It's very annoying as it can take a day or two if it's a very large torrent. 
 
Does anyone else have this problem?
 
Here are my mappings - appdata is set to R/W Slave on an UD.   Thanks in advance for any help
 
1114109374_FireShotCapture133-Highlander_UpdateContainer_-https___1d087a25aac48109ee9a15217a.thumb.png.368298e22dd121f450b9e20fa25ff687.png
 
screenshot.9.thumb.jpg.a9f59f8335b1ff7e3ae752b4e6cf66b1.jpg
What happens if you stop it from the command line doing this:

docker stop -t 60 deluge

Will it still have to check the consistency of the torrents?

Sent via Tapatalk because my wife thinks I spend too much time on the computer

Share this post


Link to post
1 hour ago, Squid said:

What happens if you stop it from the command line doing this:

docker stop -t 60 deluge

Will it still have to check the consistency of the torrents?

Sent via Tapatalk because my wife thinks I spend too much time on the computer
 

Thanks - I'll have to try this maybe tomorrow/Monday. I've just created a fresh docker instance just in case some weird plugin settings etc were causing problems, so I'm re-adding my old torrents by rechecking.

Share this post


Link to post

Hi,

 

I just updated to the new deluge and it looks like I"m also affected by the ignore upload limit issue. I'm also affected by not being able to have more than 13 active torrents.

 

Is there a way for me to downgrade back to my previous version?

 

Thanks.

Share this post


Link to post
1 hour ago, DZMM said:

Thanks - I'll have to try this maybe tomorrow/Monday. I've just created a fresh docker instance just in case some weird plugin settings etc were causing problems, so I'm re-adding my old torrents by rechecking.

Yeah, I don't use torrents (for years now), but I remember from uTorrent that if the program exited abruptly, then a check had to be done.  unRaid's default for stopping any container is 10 seconds.  If it doesn't stop in that time, then it forcibly kills the container.  The command is telling it to not forcibly kill for 60 seconds.  

 

Due to a quirk though of dockerMan, you won't be able to restart the container via the GUI if you stop it that way.  You'll have to

docker start deluge


 

If this fixes it, then I'll reissue my previously rejected PR that added a selectable timeout for stopping a container.

Share this post


Link to post
Posted (edited)
1 hour ago, Squid said:

Yeah, I don't use torrents (for years now), but I remember from uTorrent that if the program exited abruptly, then a check had to be done.  unRaid's default for stopping any container is 10 seconds.  If it doesn't stop in that time, then it forcibly kills the container.  The command is telling it to not forcibly kill for 60 seconds.  

 

Due to a quirk though of dockerMan, you won't be able to restart the container via the GUI if you stop it that way.  You'll have to


docker start deluge


 

If this fixes it, then I'll reissue my previously rejected PR that added a selectable timeout for stopping a container.

I think this is my problem.  I've noticed since I moved my appdata to an unassigned drive, I've had problems stopping and editing Dockers e.g. if i don't stop before editing, after editing I could lose the whole image i.e. I can't even go back to CA and just restore, I have to re-create from scratch.

 

Will do the delige stop test when I can, but I think I might have a bigger problem - I'll also try running from my cache to see if that removes the problem.

 

Edit: Just realised I meant docker not appdata - will try moving docker image back to my cache drive as that's easier

Edited by DZMM

Share this post


Link to post

@Squid I had a window to reboot - no joy with docker stop -t 60 deluge. 

 

I tried moving docker and the appdata back to my cache from UD.  At least moving docker and appdata back to my cache let me edit dockers without losing the whole image.

 

Logs attached - nothing looks wrong in there.

 

 

deluge.log

Share this post


Link to post
10 hours ago, DZMM said:

@Squid I had a window to reboot - no joy with docker stop -t 60 deluge. 

 

I tried moving docker and the appdata back to my cache from UD.  At least moving docker and appdata back to my cache let me edit dockers without losing the whole image.

 

Logs attached - nothing looks wrong in there.

 

 

deluge.log

seems to be working now - I've done a few restarts with no errors.  Will monitor

Share this post


Link to post
On 8/6/2018 at 8:28 PM, DZMM said:

I found this deluge thread and I'm going to see if adding ignore_resume_timestamps for it_config helps

 

https://dev.deluge-torrent.org/ticket/3044

 

 

This has definitely fixed my errors after restarting problem

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.