search

qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
28.41k stars 3.99k forks source link

speed limit does not work at all #1917

Closed rickysarraf closed 10 years ago

rickysarraf commented 10 years ago

I built qbittorrent-nox on Raspberry Pi. The version I use is: v3.1.9.2

I have not set the global speed limit. For the alternate speed limit, I have put 20 KiB for both upload and download. For time, I've scheduled it to trigger everyday at 10:00 to 21:00 hrs.

The speed limits do not apply at all. qbittorrent-nox is eating all the available bandwidth. Is this a known issue ?

rickysarraf commented 10 years ago

[General] ported_to_new_savepath_system=true

[Preferences] WebUI\Port=8090 WebUI\Enabled=true Downloads\SavePath=/media/HTPC/ Downloads\TempPathEnabled=true Downloads\TempPath=/home/pi/Torrents Downloads\ScanDirs=/home/pi/ Downloads\DownloadInScanDirs=0 Downloads\TorrentExport= MailNotification\enabled=false MailNotification\email= MailNotification\smtp_server=smtp.changeme.com MailNotification\req_ssl=false MailNotification\req_auth=false MailNotification\username= MailNotification\password= Downloads\PreAllocation=false Queueing\QueueingEnabled=true Queueing\MaxActiveDownloads=5 Queueing\MaxActiveTorrents=15 Queueing\MaxActiveUploads=5 Queueing\IgnoreSlowTorrents=true Downloads\UseIncompleteExtension=false Connection\PortRangeMin=6881 Connection\UPnP=true Connection\GlobalDLLimit=-1 Connection\GlobalUPLimit=-1 Bittorrent\MaxConnecs=500 Bittorrent\MaxConnecsPerTorrent=100 Bittorrent\MaxUploadsPerTorrent=4 Advanced\IncludeOverhead=true Connection\GlobalDLLimitAlt=20 Connection\GlobalUPLimitAlt=20 Scheduler\Enabled=true Scheduler\start_time=@Variant(\0\0\0\xf\x2%Q\0) Scheduler\end_time=@Variant(\0\0\0\xf\x4\x81\x90\x80) Scheduler\days=0 Bittorrent\DHT=true Bittorrent\sameDHTPortAsBT=true Bittorrent\DHTPort=6881 Bittorrent\PeX=true Bittorrent\LSD=true Bittorrent\Encryption=0 Connection\ProxyType=-1 Connection\Proxy\IP=0.0.0.0 Connection\Proxy\Port=8080 Connection\ProxyPeerConnections=false Connection\Proxy\Authentication=false Connection\Proxy\Username= Connection\Proxy\Password= IPFilter\Enabled=false IPFilter\File= WebUI\Username=admin WebUI\LocalHostAuth=true WebUI\HTTPS\Enabled=false DynDNS\Enabled=false DynDNS\Service=0 DynDNS\Username= DynDNS\Password= DynDNS\DomainName=changeme.dyndns.org Connection\alt_speeds_on=true WebUI\Password_ha1=@ByteArray(PASSWORD) General\Locale=en_US Downloads\TorrentExportDir=

[LegalNotice] Accepted=true

[AutoRun] enabled=false program=

rickysarraf commented 10 years ago

Nothing looks wrong to me in the cofig file. Where else would you recommend to look at ?

rickysarraf commented 10 years ago

And here's a crash that keeps happening every few hours....

05/09/2014 17:52:57 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 8090 05/09/2014 17:52:57 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP: The port mapping entry specified conflicts with a mapping assigned previously to another client 05/09/2014 17:58:19 - UPnP / NAT-PMP support [ON] 05/09/2014 17:58:19 - HTTP user agent is qBittorrent v3.1.9.2 05/09/2014 17:58:19 - DHT support [ON], port: UDP/6881 05/09/2014 17:58:19 - PeX support [ON] 05/09/2014 17:58:19 - Local Peer Discovery support [ON] 05/09/2014 17:58:19 - Encryption support [ON] 05/09/2014 17:58:19 - Embedded Tracker [OFF] 05/09/2014 17:58:19 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 8090

Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v3.1.9.2 stack trace: /lib/arm-linux-gnueabihf/libc.so.6 : __default_sa_restorer_v2()+0 [0xb64f9f20] Segmentation fault

Initially I though it would have happened because of the old version in Wheezy. For which, I compiled the latest from from Sid on it. But I still get the crash. Would you be interested in the core ?

sledgehammer999 commented 10 years ago

(open a different issue for the crash and try to do a manual full backtrace)

Does the limiting work if you set a global limit? Have you confirmed that during those hours the alternative speed limits are in effect? (the icon in the status bar changes slightly) Which version of libtorrent do you use?

rickysarraf commented 10 years ago

On Saturday 06 September 2014 12:29 PM, Ritesh Raj Sarraf wrote:

I'm not sure if I can call it a bug anymore. BTW, you should add a verbose mode for situations like these.

I just checked back the web UI. AT this time, it was supposed to use the alternative speeds, which it is not using.

Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."

rickysarraf commented 10 years ago

On Saturday 06 September 2014 01:00 AM, sledgehammer999 wrote:

(open a different issue for the crash and try to do a manual full backtrace)

Okay.. Will do this later.

Does the limiting work if you set a global limit? Have you confirmed that during those hours the alternative speed limits are in effect? (the icon in the status bar changes slightly) Which version of libtorrent do you use?

This one is very tricky. Initially it did not work. Then after you feed in the settings, interrup q-nox and restart. Still did not work. Then I chose Pause All and Resume All. And then it works.

I'm not sure if I can call it a bug anymore. BTW, you should add a verbose mode for situations like these.

Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."

sledgehammer999 commented 10 years ago

Hmm, I didn't see that you were using the -nox variant. Are you able to test with the latest code in the v3_1_x branch? There were some commits that fixed webui settings not getting saved correctly. Maybe it fixes your problem too. You didn't mention your libtorrent version.

rickysarraf commented 10 years ago

On Saturday 06 September 2014 10:03 PM, sledgehammer999 wrote:

Hmm, I didn't see that you were using the -nox variant. Are you able to test with the latest code in the v3_1_x branch? There were some commits that fixed webui settings not getting saved correctly. Maybe it fixes your problem too. But in the comments I mentioned that the settings were saved correct. I think the problem lies that q-nox is not honoring the bandwidth shaping settings correct.

How does it determine the time ? My RPi is network synced and my timezone is +5:30.

You didn't mention your libtorrent version. libtorrent is at version 0.15.10

Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."

sledgehammer999 commented 10 years ago

I am not that familiar with the nox code, I am going to look at it again. Just so you know the speed limiting is handled by libtorrent. And the 0.15.x series are really old. I only test if qbt compiles against 0.15.x. I never test if all settings are working as they should.

rickysarraf commented 10 years ago

I'll do that. I'm compiling libtorrent from Debian Sid now. Will let you know if that helps.

On Sat, Sep 6, 2014 at 10:43 PM, sledgehammer999 notifications@github.com wrote:

I am not that familiar with the nox code, I am going to look at it again. Just so you know the speed limiting is handled by libtorrent. And the 0.15.x series are really old. I only test if qbt compiles against 0.15.x. I never test if all settings are working as they should.

— Reply to this email directly or view it on GitHub https://github.com/qbittorrent/qBittorrent/issues/1917#issuecomment-54721023 .

Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."

sledgehammer999 commented 10 years ago

Thank you, because it is a mess to read the html/javascript code and trace what happens.

rickysarraf commented 10 years ago

After a day of compiling on the Pi (and also the trigger of OOM), I finally have the q-nox binary running. The version of libtorrent I'm now using is 0.16.x.

The immediate change I see is this:

Enable bandwidth management (uTP) Apply rate limit to uTP connections

Previously, for these 2, only the text was displayed. The checkboxes were never available. Which would mean that though I set the alternative speed, it was never into effect.

But then, that assumption should be wrong, given that the correct settings were written down into the config file.

Anyways, I'm gonna keep running this. Tomorrow, daytime, I should be in a better position to give you the outcome.

Thanks for your work on qBittorrent and helping me out.

Ritesh

On Saturday 06 September 2014 10:45 PM, Ritesh Raj Sarraf wrote:

I'll do that. I'm compiling libtorrent from Debian Sid now. Will let you know if that helps.

On Sat, Sep 6, 2014 at 10:43 PM, sledgehammer999 <notifications@github.com mailto:notifications@github.com> wrote:

I am not that familiar with the nox code, I am going to look at it
again. Just so you know the speed limiting is handled by
libtorrent. And the 0.15.x series are really old. I only test if
qbt compiles against 0.15.x. I never test if all settings are
working as they should.

—
Reply to this email directly or view it on GitHub
<https://github.com/qbittorrent/qBittorrent/issues/1917#issuecomment-54721023>.

Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."

Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."

rickysarraf commented 10 years ago

I can confirm now that updating the libraries fixes the problem.

sledgehammer999 commented 10 years ago

Thank you for following up on your opened issue. I am glad you solved it.