binhex / arch-qbittorrentvpn

Docker build script for Arch Linux base with qBittorrent, Privoxy and OpenVPN
GNU General Public License v3.0
397 stars 46 forks source link

qBT restarts while checking large torrent #237

Open hell001 opened 1 month ago

hell001 commented 1 month ago

This has been happening for months and I refrained from posting here because I 'm not sure i have enough info to help diagnose. but im not sure what else to do at this point. when i add larger torrents (150gb+), and force recheck them before seeding, it never makes it all the way and im pretty sure its the "qbittorrent-nox" process that restarts (i dont believe its the whole docker container that restarts? although i cannot access the containers console from unraid, but it says the container is still running). the logs dont seem to show anything useful and loops the following lines:

[info] qBittorrent not running
[info] Privoxy not running
[info] Removing session lock file (if it exists)...
[info] Attempting to start qBittorrent...
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...
[info] qBittorrent process listening on port 8080
[info] Attempting to start Privoxy...
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...
[info] Privoxy process listening on port 8118
------> [info] qBittorrent not running <------------------------- LOOP STARTS FROM THIS POINT AGAIN
[info] Removing session lock file (if it exists)...
[info] Attempting to start qBittorrent...
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...
[info] qBittorrent process listening on port 8080

openvpn is being used and im 99% positive the problem is not on the provider's end as i have been trying to do this for months and every time it doesnt finish. i have also tried adding additional remotes in the ovpn file just in case per A20 of the faq, but still nothing. i can also confirm the torrent file itself is fine as i have tried on multiple other clients and hosts that are not running binhex-qBT

i do apologize as i am sure this is not enough info, but please let me know what else i can provide. i have also ran the container in debug mode but there are still no errors there. i could simply skip the hash check but i would prefer to get to the root cause of the issue