qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
27.8k stars 3.92k forks source link

qB v4.4.1 Monitored Folders Not Pulling .torrents UNLESS restart #16712

Closed wiffleman closed 2 years ago

wiffleman commented 2 years ago

qBittorrent & operating system versions

qBittorrent 4.4.1 (binhex/arch) Operating System: Linux Docker Qt: 6.2.3 Libtorrent: 2.0.5.0

What is the problem?

Watched folders are NOT pulling torrents UNLESS on container restart.

Steps to reproduce

  1. Start docker container - boots fine, can download and manually add .torrent files/magnet links.
  2. In preferences - have "Automatically add torrents from" folders set-up. Two monitored folders with the volumes properly mounted.
  3. Add .torrent file to Monitored Folder. At this stage, the torrent is NOT added
  4. Upon container restart and subsequent reboot of qBittorrent - the torrent is then added

Additional context

No response

Log(s) & preferences file(s)

No response

glassez commented 2 years ago

Perhaps there are some problems with the workability inside the Docker container (note that Docker is not officially supported). Could you try to enable recursive mode for your watched folders and test how it behaves? It uses a different way of monitoring, so that might help.

wiffleman commented 2 years ago

No dice changing changing the watched_folder.json to recursive.

Such an interesting observation: I actually have two instances of this docker container fired up - one for personal torrenting, and a separate for seedbox on a different port. My PERSONAL use one is connected to Jackett and the other -arr containers, and this one is able to pull .torrents from its '/blackhole' directory NO PROBLEMS. I created the Seedbox container with the EXACT parameters and this second instance is not working.... I cannot seem to identify ANY differences in the setup, and I am sure the mounts are working properly (this has to be the case if it is pulling the .torrent files from the watched folder on boot).

So weird.

wiffleman commented 2 years ago

Another observation: I realized that I don't actually need to re-start the container altogether. If I remove the monitored folder, save settings, and re-enter it - it will re-scan and pick up any .torrents in the folder.

wiffleman commented 2 years ago

Solved - was an issue with folder permissions.

Ralpie79 commented 2 years ago

Can you tell me how you solved this, having the same problem. Running this on Truenas Scale and can't seem to get it to load.

EDIT: Nevermind figured out what you did, went back to Truenas and tried recursive setting on the folder and seemed to pick it up. Thanks

Feriman22 commented 1 year ago

I don't know why it works, but I've tested it several times and that's how I got it to work:

1., Put one torrent file into the watched folder 2., Give 777 permission to it 3., Restart the Docker container 4., From now on, it will load the torrent file you have already copied, and all the others you copy afterwards, even without 777 rights

Maybe it works for native qBittorrent installations as well.

I am pretty sure it is a bug in qBit. I have seen the same problem in many places on the internet, on different operating systems, even years ago. I'm using v4.5.5 (which is the latest at the moment), and the problem exists on that one too.