starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Torrent / Tracker status not resetting #13094

New issue

Closed

opened 2026-02-21 23:32:51 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 23:32:51 -05:00

Owner

Originally created by @reyaz006 on GitHub (Feb 19, 2022).

qBittorrent & operating system versions

4.4.1 @ qBittorrent-CI_Windows-x64_libtorrent-1.2.15
Windows 8.1 6.3.9600

What is the problem?

For a "Stalled" torrent with a tracker stuck at "Updating" status, pressing Pause/Resume several times does not change anything.

When it's Paused, the tracker is still Updating. It should reset its status since the torrent is paused.

When Resuming from Paused, torrent status reverts to "Stalled" immediately. It should be Downloading instead and trying to contact tracker again from scratch.

Steps to reproduce

Accumulate 40000 torrents over the years.
Don't remove torrents over the years.
Remove files when not needed over the years.
Always have this issue.

Additional context

No response

Log(s) & preferences file(s)

qBittorrent_redacted.zip

Originally created by @reyaz006 on GitHub (Feb 19, 2022). ### qBittorrent & operating system versions 4.4.1 @ [qBittorrent-CI_Windows-x64_libtorrent-1.2.15](https://github.com/qbittorrent/qBittorrent/suites/5322558951/artifacts/165772584) Windows 8.1 6.3.9600 ### What is the problem? For a "Stalled" torrent with a tracker stuck at "Updating" status, pressing Pause/Resume several times does not change anything. When it's Paused, the tracker is still Updating. It should reset its status since the torrent is paused. When Resuming from Paused, torrent status reverts to "Stalled" immediately. It should be Downloading instead and trying to contact tracker again from scratch. ### Steps to reproduce 1. Accumulate 40000 torrents over the years. 2. Don't remove torrents over the years. 3. Remove files when not needed over the years. 4. Always have this issue. ### Additional context _No response_ ### Log(s) & preferences file(s) [qBittorrent_redacted.zip](https://github.com/qbittorrent/qBittorrent/files/8102551/qBittorrent_redacted.zip)

deekerman closed this issue

2026-02-21 23:32:55 -05:00

deekerman commented

2026-02-21 23:33:00 -05:00

Author

Owner

@ghost commented on GitHub (Feb 19, 2022):

Announces happen in a queue. When you see updating, that means it's either in a queue or announce is in process. If you want announces to finish fast then increase number of "Max concurrent HTTP announces".

@ghost commented on GitHub (Feb 19, 2022): Announces happen in a queue. When you see updating, that means it's either in a queue or announce is in process. If you want announces to finish fast then increase number of "Max concurrent HTTP announces".

deekerman commented

2026-02-21 23:33:00 -05:00

Author

Owner

@reyaz006 commented on GitHub (Feb 20, 2022):

I changed "Max concurrent HTTP announces" to 500 000 and it kind of changed how the UI displays information. I can see that sometimes tracker status goes from Not working to Updating. But then it gets stuck in either state for some time. Though, it doesn't change the fact that torrents still immediately become Stalled after resuming. Force reannounce does not seem to have any effect. I still have torrents with trackers stuck in Not working or Updating. I checked with other client and these torrents can download fine.

Is there any place where this queue can be seen and managed manually? I'm pretty sure it's not being handled effectively now. I can't download torrents from certain trackers for more than a month due to them being stuck.

Is there a way to check the actual process and output of announcement process? So we could debug it by checking request/response times, response body etc. I'm not having any problems accessing these URLs directly with any browser or other torrent clients, but they are always stuck in qbt.

@reyaz006 commented on GitHub (Feb 20, 2022): I changed "Max concurrent HTTP announces" to 500 000 and it kind of changed how the UI displays information. I can see that sometimes tracker status goes from Not working to Updating. But then it gets stuck in either state for some time. Though, it doesn't change the fact that torrents still immediately become Stalled after resuming. Force reannounce does not seem to have any effect. I still have torrents with trackers stuck in Not working or Updating. I checked with other client and these torrents can download fine. Is there any place where this queue can be seen and managed manually? I'm pretty sure it's not being handled effectively now. I can't download torrents from certain trackers for more than a month due to them being stuck. Is there a way to check the actual process and output of announcement process? So we could debug it by checking request/response times, response body etc. I'm not having any problems accessing these URLs directly with any browser or other torrent clients, but they are always stuck in qbt.

deekerman commented

2026-02-21 23:33:00 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Sep 30, 2024):

4.4.1
Windows 8.1 6.3.9600

Version(s) obsolete.

Thank you for your contribution, we are starting to close all old/stale/obsolete tickets.

Please update to latest qBittorrent 5.0.0 ATTOW.

If any issues are experienced, please open a new ticket.

Windows Users: (Note: Windows 10 1809+ / Windows Server 2019 required as minimum)

@xavier2k6 commented on GitHub (Sep 30, 2024): >4.4.1 >Windows 8.1 6.3.9600 Version(s) obsolete. Thank you for your contribution, we are starting to close all old/stale/obsolete tickets. Please update to latest qBittorrent 5.0.0 ATTOW. If any issues are experienced, please open a new ticket. Windows Users: (Note: Windows 10 1809+ / Windows Server 2019 required as minimum)

deekerman referenced this issue

2026-02-22 03:31:21 -05:00

Meta - Generic announcement posted in locked topics where general users cannot react #16902