Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qbittorrent-nox 4.2.1 ignoring schedule of alternative rate limits #12078

Open
Oriann opened this issue Feb 26, 2020 · 13 comments
Open

qbittorrent-nox 4.2.1 ignoring schedule of alternative rate limits #12078

Oriann opened this issue Feb 26, 2020 · 13 comments
Labels

Comments

@Oriann
Copy link

Oriann commented Feb 26, 2020

Please provide the following information

qBittorrent version and Operating System

qbittorrent-nox 4.2.1
FreeBSD 21.1

What is the problem

Qbittorrent ignoring scheduled alternative rate limits from today

What is the expected behavior

Setting scheduled rate limits, should apply after hitting save

Steps to reproduce

Start qbittorrent, set scheduled rate limits, hit Save, start seeding and just watch this
image

Extra info(if any)

Issue started today when I have toggled Torrent queuing, toggling it back does not reverse problem with limiter.

@FranciscoPombal
Copy link
Member

In Preferences -> Speed, which "Rate limit settings" checkboxes (at the bottom) do you have set? See if you can reproduce the problem with all of them checked.

@FranciscoPombal FranciscoPombal added the Waiting info Waiting for participants to supply more info/fulfill template requirements label Feb 26, 2020
@Oriann
Copy link
Author

Oriann commented Feb 26, 2020

In Preferences -> Speed, which "Rate limit settings" checkboxes (at the bottom) do you have set? See if you can reproduce the problem with all of them checked.

Yep, I tried to check them all restart qbittorrent, the tries to uncheck all and restart..

Now qbit is ignoring even global rate settings...wtf is going on

@FranciscoPombal
Copy link
Member

You should have them all checked if you want the limits to always be respected.

Now I see that you mention "scheduled". I have a sneaking suspicion the limits might just be applied the following time period. So, suppose it is currently 16:00 and you set scheduled limits to run from 15:00 - 18:00. Then they might just be applied the following day. Or qBIttorrent needs to already have been started at the beginning of the interval. But I'm not sure. Try to isolate the problem a bit more and post here the results.

@Oriann
Copy link
Author

Oriann commented Feb 26, 2020

So issue for me is kinda resolved, but it was too easy.

Steps how to reproduce:
1.Change rate limits then save
2.Change manually Alt/Global rates with bottom icon.
3.Change rate limits once more and now its jammed and qbittorrent stops responding to any rates.

Steps to problem solve:
1.Untick alt rate limits, restart qbittorrent
2.Set correct rates and then tick alt rate limits
3.restart qbittorrent once more and problem solved.

I think there is some problem in qbit core because few switches between rate limits make it sick, pls try to look at it in code.

@FranciscoPombal
Copy link
Member

Sorry, could not reproduce. @thalieht, can you try to reproduce please?

@FranciscoPombal FranciscoPombal added Can't reproduce Issues that cannot be reproduced Help wanted and removed Waiting info Waiting for participants to supply more info/fulfill template requirements labels Feb 26, 2020
@thalieht
Copy link
Contributor

This has been reported many times but i never could reproduce.

@FranciscoPombal
Copy link
Member

@Oriann

Any chance you can provide a bit more precise steps? From starting the program, specifying when you start the torrents, etc

@Oriann
Copy link
Author

Oriann commented Feb 26, 2020

So It appeared once more for me

Starting position

1.
image
2.
image
3.
image

What I have changed to reproduce issue:

1.
image
2.
image
3.
image

Now trying to revert that, almost impossible again.

@Oriann
Copy link
Author

Oriann commented Feb 26, 2020

So I have successfully reverted back to "Starting position" config then restarted qbittorrent and everything went to normal again.

Issue can be:

  1. Maximum number of upload slots per torrent - tick or value
  2. Apply rate limit to peers on LAN - tick
  3. Torrent Queueing - values or tick

EDIT:
1.Unticked/ticked no difference
3.Unticked - limiter starts doing spikes - limited to 2MiB spiking to 3.4MiB and then reverts under limit, this is happening continuously
2.Unticked - speed grows over limit and does not come back, once I tick this setting back, limiter does not recognize any changes, reverting to normal can be done with setting everything back to original (as stated on screenshots) and rebooting qbittorrent

Does it help a little ?

@FranciscoPombal
Copy link
Member

FranciscoPombal commented Feb 27, 2020

@Oriann Thanks for the details. I just noticed I failed to activate the scheduler in my testing, so that could be a reason I was not able to reproduce. I will test this when I have more time for this.

@glassez mind taking a look at this?

@FranciscoPombal FranciscoPombal removed the Can't reproduce Issues that cannot be reproduced label Feb 27, 2020
@Oriann
Copy link
Author

Oriann commented Mar 3, 2020

So new info, after 2 scheduled server reboots, the bug is back in qbittorrent, now I cannot revert the issue even after appling commands I have written here. I am forced to shutdown qbittorrent jail because I cannot control limits now, qbittorrent is eating all my bandwidth with constant speed spikes.

Is there some kind of temporary hotfix ? Or is possible to downgrade without losing data and torrent queue ?

@Xaldeon
Copy link

Xaldeon commented Mar 4, 2020

Mine is always applying the alternative rates whether the option is enabled or not. Rebooting does not fix this issue.

@Oriann
Copy link
Author

Oriann commented Mar 4, 2020

Mine is always applying the alternative rates whether the option is enabled or not. Rebooting does not fix this issue.

This is starting to complicate things..I have started qbittorrent today for a while and everything was good, in the afternoon it started to ignkre limits again. I wasnt able to fix it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants