mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Torrents are not seeding after hibernate #16516
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#16516
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @merlin2222 on GitHub (Jan 5, 2025).
qBittorrent & operating system versions
qBittorrent v5.0.3 x64
Windows 10 Pro x64 (22H2) OS Build 19045.5247
qt6 lt20
What is the problem?
Torrents are not seeding after resuming from hibernate.
Steps to reproduce
Additional context
I don't find my torrents seeding on the torrent site I am using after resuming from hibernation. After I select the torrent and press "Stop" icon and after that "Start" icon torrent is reported as seeding.
Log(s) & preferences file(s)
qbittorrent.log
@stalkerok commented on GitHub (Jan 5, 2025):
Related/Duplicate of https://github.com/qbittorrent/qBittorrent/issues/20305 https://github.com/qbittorrent/qBittorrent/issues/17898 https://github.com/qbittorrent/qBittorrent/issues/19961
What tracker status and message did you receive from the tracker before pressing stop/start? Also interested in the intervals. Please make a screenshot.
@glassez I think this change should be rolled back.
@stalkerok commented on GitHub (Jan 5, 2025):
Log:
@merlin2222 commented on GitHub (Jan 5, 2025):
It seems to be working fine now. Thank you for your assistance!
Br
P.S. I do believe this was solved with the latest version that I downloaded few days ago as it was not working with previous versions
@glassez commented on GitHub (Jan 14, 2025):
Please remind me, has it been confirmed by anyone that libtorrent itself reannounces after hibernation? Where did this quote come from?
@merlin2222 commented on GitHub (Jan 14, 2025):
It behaves oddly - if the hibernation lasts short, say less than 5 minutes, I find torrents seeding but if the hibernation lasts longer, say more than half of hour, then they are not seeding.
@stalkerok commented on GitHub (Jan 16, 2025):
I had no problems both before and after this change https://github.com/qbittorrent/qBittorrent/issues/17898#issuecomment-1631123585. I spent quite a bit of time trying to reproduce this but to no avail, the trackers always started working.
This is my quote. https://github.com/qbittorrent/qBittorrent/issues/19961#issuecomment-1817944519
I don't think re-announcing helps anything, as the problem occurs not only with announcements, but also with RSS https://github.com/qbittorrent/qBittorrent/issues/20305. It's just like there's no internet.
Also https://github.com/qbittorrent/qBittorrent/issues/17898#issuecomment-1637120847
@merlin2222 commented on GitHub (Jan 16, 2025):
I can see that. I am using WiFi to conenct to my router and it usually takes 1-2 seconds for the connection to be re-established after waking up from hybernation. Can that explain why external IP is not detected?
P.S. I am willing to do as much as I can to help you guys solve this. As this issue can be easilly reproduced on my notebook do not hesitate to ask for any additional information you may need.
@merlin2222 commented on GitHub (Jan 16, 2025):
If I stop seeding on the client, or exit the client, the tracker is still stating that seeding is active for some time after that. Maybe there is some refresh interval set on the tracker side which would explain while seeding works after short hybernation.
However, if hybernation lasts longer than I find torrents not seeding.
@stalkerok commented on GitHub (Jan 16, 2025):
?
@merlin2222 commented on GitHub (Jan 17, 2025):
Before Stop/Start:
After Stop/Start:
What intervals are you referring to?
@stalkerok commented on GitHub (Jan 17, 2025):
Please make the same two screenshots but with these columns. But this time, don't hit stop/start, but wait for the announce interval.
@merlin2222 commented on GitHub (Jan 17, 2025):
After 15 minutes hybernation:
I'll post next one after the announce period expires.
@merlin2222 commented on GitHub (Jan 17, 2025):
After announce period expired:
@stalkerok commented on GitHub (Jan 17, 2025):
Good. Try doing this
How long will it take for the tracker to enter the “Working” state?
@merlin2222 commented on GitHub (Jan 17, 2025):
Tracker enters the "Working" state in app. 1 minute.
@stalkerok commented on GitHub (Jan 17, 2025):
I wonder why you have such an interval of tracker announce after hibernation? After a failed attempt, the min interval is 17 seconds, then 1 minute and so on, the max is 1 hour. To get such an interval (43 minutes) you need a lot of failed attempts. https://github.com/arvidn/libtorrent/blob/RC_1_2/src/announce_entry.cpp
https://github.com/user-attachments/assets/34415a84-9dd9-4ed4-abad-c4040672dacc
https://github.com/user-attachments/assets/3e93ad5a-daec-41d6-8282-932b7f101d4e
@glassez I hope this helps in some way.
@merlin2222 commented on GitHub (Jan 17, 2025):
After folowing your procedure after tracker enters "working" state "Next announce" is set to 45 minutes, the same interval it is set after hybernation, so it may not be a result of any failed attempts.
@merlin2222 commented on GitHub (Jan 17, 2025):
I was expecting that after hybernation the tracker is set to 17sec, if it fails than to 1 minute and so on, but that is not what is happening - after waking from hybernation I find it set to 45 minutes, which is the same interval that was set at the moment I initiate hybernation.
It seems that client wakes from hybernation set to 45 minutes as it was before hybernation instead of 17sec. Could that be the problem?
@merlin2222 commented on GitHub (Jan 17, 2025):
Maybe you can configure the client to set "next announce" to 17sec whenever it re-establishes online status?
@stalkerok commented on GitHub (Jan 17, 2025):
Perhaps this is the interval received from the tracker, but you should have a failed attempt after the system wakes up, as indicated by the message “The requested name is valid, but no data of the requested type was found”. This interval should reset to the minimum interval.
@merlin2222 commented on GitHub (Jan 17, 2025):
Yes, it seems that interval interval is not reset to 17sec inspite of the message "The requested name is valid.."
Btw, from what I can tell after waking from hybernation the client becomes active before Internet connection is re-established which should indeed cause failed attempt but for some reason that is not happening.
@merlin2222 commented on GitHub (Jan 17, 2025):
Are failed attempts after hybernation written in the client's log? Would it help to send you the log?
@merlin2222 commented on GitHub (Jan 17, 2025):
So, tto sum it up: the message after hybernation indicates no connection but the interval is not reset?
Is that correct?
@somethingstupid2 commented on GitHub (Jan 31, 2025):
I'm having this issue as well. I ran DNSLookupView because the error I was getting was "no such host is known."
Upon waking up from Hibernation, QBT will try to resolve the tracker's host name and get an Error 9701 (DNS record does not exist.) Even if I force a reannounce, QBT will not try to resolve the host name after it has received Error 9701.
Afterwards, it seems as though QBT will simply stop trying for an indeterminate amount of time, requiring a restart of the program.
@SynapseScribe commented on GitHub (Apr 16, 2025):
happens to me too when using an external hyper-v vswitch (bridge), after resuming from sleep. the torrents are not resumed and i get error "no such host is known", even if i added the ip - name in the hosts file for quick lookup. Note that i am using also adguardhome
@nativ69 commented on GitHub (Dec 8, 2025):
same here.
after hibernation qBittorrent is unable to resolve the tracker(s) hostname, so it won't seed until restart of qBittorrent.
@SynapseScribe commented on GitHub (Dec 8, 2025):
i ended up hardcoding the [IP] [TRACKER_DOMAIN] into windows hosts and now it works fine for me
@nativ69 commented on GitHub (Dec 8, 2025):
that's not a good solution, especially for trackers behind CDN network like cloudflare.
@SynapseScribe commented on GitHub (Dec 8, 2025):
definetely it's not the solution, but it works in cases where tracker's ips are static. it's a workaround for users not a fix in the qbittorrent client. i think it's clear enough