Open pixelnull opened 1 year ago
Peer ID: "-qB5300-"
? Official is -qB4500- for this version.
Peer ID: "-qB5300-"
? Official is -qB4500- for this version.
Ah, it's a mispaste or a typo of some kind. It's -qB4500- in the logs.
Don't run it as a background daemon if you are. Run it in the foreground and see if there is an error displayed. Not all errors go to the log file. See here : https://github.com/qbittorrent/qBittorrent/issues/18182
Don't run it as a background daemon if you are. Run it in the foreground and see if there is an error displayed. Not all errors go to the log file. See here : #18182
Thanks for that, but it's not running as a daemon only. Additionally it's actually stalled with downloads saying "stalled" with no transfer speed. The issue that they have with the UI not updating doesn't seem to be happening with my issue. That bug also looks like it from an odd piece size on a single torrent. The stalling happens after a set amount of time regardless of what torrents it's got.
Also, a general addition for this is that I am now using cron to killall and then reopening QBT every 3 hours. So, if any logs/testing needs the stalled state, please let me know as I would need to stop the cronjob and allow it time to get to the state.
I am having the exact same issue. Loads of problems and having to manually restart, change ports, and do whatever it takes for the downloads to start.
Looking for any kind of update on this. This is still an issue.
I see similar symptoms with the no-x version 4.6.2 running on Debian with a 6.1 kernel on ARM. While transfers are not entirely stalled, they move at tens of kb/s rather than my normal rates.
Inspecting virtual memory (using htop) or:
cat /proc/$qBittorrentPID/status | grep VmSize
I've observed that the problem manifests when qbittorrent-nox
's virtual memory is around 450 GB on a machine with 4 GB RAM. Currently, virtual memory use is 250 GB, and speeds are fine. Every time I've had an issue, it's when virtual memory has been sitting much higher. I suspect qbittorrent is memory mapping all its torrents, and this exhausts the kernel's memory which impacts download/upload throughput. qBittorrent itself, through all of this, is only using about 10% of available RAM.
I've tried to drop caches, following instructions from https://linuxconfig.org/clear-cache-on-linux. That frees some kernel memory but does not help with slow transfers.
For me it's just showing that dht nodes are 0 and downloading doesn't start. The issue is only for qbittorrent v4.6.2 because I tested another app and it's downloaded files just fine.
I did more digging, and what I reported is the same as #19914.
qBittorrent & operating system versions
qBittorrent: 4.5.0 x64 Operating system: Manjaro 5.15.84-1-MANJARO KDE/Plasma (all packages have been updated) Qt: qt5-base 5.15.7+kde+r177-1 & qt6-base 6.4.1-1 libtorrent-rasterbar: libtorrent-rasterbar 1:2.0.8-2
What is the problem?
All DHT and Torrents connections stall after a few hours. This is regardless of VPN state and # of seeders in the torrent. I don't know exactly when it started, but QBT has started silently stalling on all running torrents after a certain amount of time. DHT nodes connected stat also drops to 0.
As it fails silently, I don't know about how long it takes to happen, too long to troubleshoot effectively though, 3-8 hours.
The only thing that seems to fix the issue with QBT is restarting the application.
Steps to reproduce
Start QBT, wait. Nothing else is needed. Once stalled, restarting QBT, and only QBT, fixes it temporarily but immediately. DHT nodes start to connect again within seconds, and pause/unpause of torrents will immediately start downloading again.
Additional context
It's a VM with KVM/QEMU. 4 vCores, 8Gb Ram, 10Tb of free space on a 20Tb array. It has it's own dedicated physical NIC.
Troubleshooting I've done so far:
I have not been able to figure this out for weeks. I'd use a different client but this box is supposed to be a set and forget for radarr and sonarr and QBT has worked well so far so I'd prefer to use it.
Log(s) & preferences file(s)
qBitorrent.conf
most recent qbittorrent.log
^^^ This log ends at me closing QBT in a stalled state, I did not remove any lines. Adding torrents, removing torrents, changing settings, etc all work. It's just stalled.