Open Oriann opened 4 years ago
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.
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
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.
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.
Sorry, could not reproduce. @thalieht, can you try to reproduce please?
This has been reported many times but i never could reproduce.
@Oriann
Any chance you can provide a bit more precise steps? From starting the program, specifying when you start the torrents, etc
So It appeared once more for me
1. 2. 3.
Now trying to revert that, almost impossible again.
So I have successfully reverted back to "Starting position" config then restarted qbittorrent and everything went to normal again.
Issue can be:
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 ?
@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?
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 ?
Mine is always applying the alternative rates whether the option is enabled or not. Rebooting does not fix this issue.
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.
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
Extra info(if any)
Issue started today when I have toggled Torrent queuing, toggling it back does not reverse problem with limiter.