Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitored Folder for automatic add files not working correctly #5966

Closed
yuengling opened this issue Nov 19, 2016 · 36 comments
Closed

Monitored Folder for automatic add files not working correctly #5966

yuengling opened this issue Nov 19, 2016 · 36 comments
Labels

Comments

@yuengling
Copy link

yuengling commented Nov 19, 2016

-Windows 8.1 host machine
-Shared folder access setup correctly. Have networked drives that downloads are automatically grabbed from in qBittorrent settings.
-Need to restart program each time for it to recognize newly added files. Does not automatically work.
-Is there a config setting to update or force monitored folder refresh interval?

@Makeshift
Copy link

Currently having the same issue on a Win10 host machine. If your black hole is on a network drive, qBittorrent will not see new torrents being added until you restart it.

@davi1td
Copy link

davi1td commented Apr 27, 2017

So what is the deal here? Any updates? exact same config and doing the same thing, Win10 .torrents saved to share, only picks up new .torrents on restart, clearly something is wrong ... anything we can do to help resolve this?
Thanks
-TD

@Crunch77
Copy link

Still an issue.
Win10 on VirtualBox accessing shared folder.

@Yoshi900
Copy link

Yoshi900 commented Apr 6, 2018

finding this also in 4.0.4 I think it might have been working in 4.0.2 however not sure if I can downgrade without losing all my settings / torrents.

@robertlankford
Copy link

Yep. Seeing the same issue. What a bummer.

@enormouspoon
Copy link

enormouspoon commented May 2, 2018

Glad to see this is presumably not user error. Hopefully a workaround or fix comes soon.

[Edit] just some more details on the issue in case it helps folks:
Virtualization: VirtualBox 5.2.8
Host OS: Windows 10 Pro 1709
Guest OS: Windows 10 Pro 1709
qBittorrent 4.0.4

Host folder mounted to Guest as network mapped drive and added to qBittorrent as "Monitored Folder". qBittorrent does not auto-add torrents saved to this monitored folder, regardless if torrent is added on host or guest side. Added torrents are only detected and auto-added when qBittorrent is first starting up or restarted. Monitored folder (at least in my case) is the drive root (i.e., H:) and not a sub-directory (i.e., H:\folder_to_watch)

[Edit2] Looks like this has been an issue (#4131) since 11/16/15, so it may be pending for awhile. I haphazardly created a cmd batch program to open all files in my watch directory every 60 seconds. When combined with qBT's option to remove torrent files when added, it works good enough for me for now. Obviously use at your own risk.

:loop
for %%f in (H:\*) do %%f
timeout /t 60 /nobreak >nul
goto loop

@ghost
Copy link

ghost commented Sep 15, 2018

Was this ever fixed? I'm using v3.3.7 on a pi and it still not picking up the *.torrent files when dropped into the specified folder.

@IamGimli
Copy link

IamGimli commented Oct 9, 2018

Not fixed, still an issue for me running on v4.1.3.

@bazsodombiandras
Copy link

Still an issue with version v4.0.3 on Ubuntu 18.04. Sometimes it picks up newly added torrents from the monitored folder, sometimes it doesn't (I have no idea what it depends on). Restarting qBittorrent makes it pick up the new torrent. The monitored folder is a subfolder of a folder shared trough Samba so that it can be accessed from Windows.

@matthaerle
Copy link

matthaerle commented Feb 22, 2019

I too am seeing this issue with a monitored folder on a samba share.
It looks like it is a shortcoming in the C++ FileSystemWatcher ability.
Maybe if they could add a manual refresh button to check for new files.

If you're on Linux I found this workaround.
https://stackoverflow.com/questions/27412061/on-ubuntu-is-there-a-way-to-automatically-move-files-to-another-directory-as-th

I set it to grab the torrent files from the samba share to a directory on my linux box and it moves once a minute and Qbittorent is able to see the file when it gets moved.

@hekimgil
Copy link

hekimgil commented Aug 9, 2019

This is still an issue. I had that happen in two machines: a Windows 10 host and an iMac host. Both machines use VirtualBox to run an Ubuntu machine. The torrent files are stored on a shared folder.

qBittorrent does not see the newly added torrent files until it is restarted.

A manual recheck button, as suggested by matthaerle, may help until the issue is fixed.

This is totally a random guess but could the problem be related to Ubuntu updating (upgrading) while qBittorrent is open? It may be that both machines first started to experience this issue after an apt upgrade while qBittorrent was open? I may be wrong but maybe others can confirm if this is really the case?

@AndyScull
Copy link

Had this problem appear last week after I apt upgraded my debian 9 box.
It seems to be tied to SMB versions and maybe something was introduced in last linux updates that broke or changed how they work.
First, the problem wasn't with qBittorrent - after this upgrade I couldn't mount my shares from Win7 PC with same fstab, got error 121 when running mount -a. Adding vers=2.1 in fstab options allowed me to mount shares but then qBittorrent's monitoring stopped working on them.
Fix was: remove vers=2,1 from fstab option and add two registry entries on PC hosting the shares:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache=1
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size=3

After I changed the values and rebooted my Windows PC, one share correctly mounted on Debian box without Vers=2.1 option in fstab, this share works correctly in qBittorrent and all torrents I throw in there are immediately picked up.
Second share on same PC is still mounted with vers=2.1 option and qBittorrent does not see new torrents in it.

I am not a programmer so I am not sure it is qBittorrent's fault but maybe the mechanism of detecting new torrents need to be changed for these new SMB protocols. Or it is some bug in linux cifs module not allowing something on newer smb shares, dunno.

@oliroe
Copy link

oliroe commented Jun 28, 2020

Has anyone come up with a workaround for this issue. I've scheduled restarting qBittorrent to pick up items in the watched folder but wondered if there was anything better. Not sure why it won't poll the location, must only do it when the app starts.

@hekimgil
Copy link

Everytime I add new files, I go to Preferences --> Downloads --> Monitored Folder to remove and readd the folder location. The application checks that location only when it is first started or when there is an update in the monitored folders list. Updating the list seems faster than closing and restarting the application.

I am so suprised that this has not been handled for such a long time. A manual recheck button could have made things much easier until the problem itself could be solved.

To repeat some background information: I use qBittorrent on Ubuntu systems on a VirtualBox host with a shared folder that resides on the host machine and is mounted on the Ubuntu guest. I have been using it without any problems for a long time but at a certain point several years ago, qBittorrent's automatic check started to fail in all the machines (both Windows 10 and MacOS hosts) at around the same time. Since it can check the folders on restart or on updating of the monitored folder lists, it does not seem to be an access issue.

@oliroe
Copy link

oliroe commented Jun 29, 2020

Yeah, really frustrating as its my only issue using Qbit. It seems like it's not platform specific as I'm using the linuxserver docker on a Synology NAS with the app, download location and blackhole all on the same machine. I don't see how it can be permissions either when it works with a restart or changing the location, it just mustn't be polling the location after the initial start/save.

There doesn't seem to be anything obviously wrong here
https://github.com/qbittorrent/qBittorrent/blob/master/src/base/scanfoldersmodel.h

@EsEnZeT
Copy link

EsEnZeT commented Dec 15, 2020

Bug still exists - qBittorrent-nox does check only on startup, later new files added to monitoring directory are ignored.

Debian 10 with fuse mount.

CC: @Chocobo1 @FranciscoPombal @glassez

@Macht59
Copy link

Macht59 commented Mar 2, 2021

The same issue appears with monitoring webdav mounted directory with davfs2 on Arch Linux.
Looks like I should find another solution as network directories are not going to be monitored.

@hekimgil
Copy link

Wow, it has been sooo many years but this issue finally seems to have been solved. This functionality started to work again for me... A big "thank you" to whoever fixed it.

@TamalesEnMiPinata

This comment has been minimized.

@shockrift
Copy link

shockrift commented Jul 8, 2021

issue appears to have resurfaced with network shares on 4.3.6 tested in several environments where 4.3.5 was working correctly and now not so. as shown here mapped drive M is netshare and C is local.
image

Edit: #15127 < issue is indeed related to unc paths as expected.

@GetStreamlined

This comment has been minimized.

@Gwyll
Copy link

Gwyll commented Jul 15, 2021

I think the problem should be around the new watch options in 4.3.6.
Downgraded to 4.3.5.

@glassez
Copy link
Member

glassez commented Jul 16, 2021

I think the problem should be around the new watch options in 4.3.6.

Yes.
Issue #15127.
Closed by #15137.
Possible workaround in qBittorrent v4.3.6 is adding dummy (but existing) local watched folder with recursive option enabled.

@rmrf-sl4sh
Copy link

Having this problem out of nowhere now, worked for years without missing a beat. v4.3.5 on fedora 34 server

@Bluecyph

This comment has been minimized.

@rmrf-sl4sh
Copy link

Still problematic with 4.3.9

@glassez
Copy link
Member

glassez commented Dec 12, 2021

Still problematic with 4.3.9

What exactly is your problem? You have to provide all the required information, otherwise your comment is just "zilch".

@rmrf-sl4sh
Copy link

rmrf-sl4sh commented Dec 12, 2021

The same problem people have been describing for months: the watch folder. qbittorrent doesn't auto-load .torrent files when they're dropped in the directory set up as the watch dir.

If this doesn't clear it up, give me a more specific request than "all the required information"

edit: it appears this issue was raised in 2016. it's been 5 years.

@rmrf-sl4sh
Copy link

Still problematic with 4.3.9

What exactly is your problem? You have to provide all the required information, otherwise your comment is just "zilch".

So are you going to help?

@Bluecyph
Copy link

Monitored folder not working for me on v4.3.9

Why is my reply marked as spam, I was just saying that it is still happening on 4.3.9

@glassez
Copy link
Member

glassez commented Dec 15, 2021

@jdqw210
@JorellAponte

This Issue (i.e. Topic on this Bug tracker) is too old. The code of "Watched folders" feature has been changed several times since then, including it underwent a fairly deep redesign relatively recently. So it is unlikely that you have exactly the same problem that the Issue author reported. If you have problems with "Watched folders" and you really want to help fix qBittorrent, then please open a new Issue with all the required data according to Contributing Guidelines .

P.S. Even if you really believe you have exactly the same problem as described in some existing Issue the comments like "Me too" is discouraged. You should at least provide the minimum set of information that is usually required to create an Issue.

@glassez glassez closed this as completed Dec 15, 2021
@rmrf-sl4sh

This comment has been minimized.

@WoodpeckerBaby
Copy link

WoodpeckerBaby commented May 25, 2023

Same issue on 4.5.2 Win 10 qt6.

I'm asking it to monitor some folders in Google Drive desktop on Win 10.

Only reliably scans for torrents at launch. Then, it scans successfully when the drive/system/network is not busy.

@Feriman22
Copy link

Same issue with Docker and qBit v4.5.5

@ICE0124
Copy link

ICE0124 commented Mar 17, 2024

Same issue with docker and qbit 4.6.3

@qbittorrent qbittorrent locked and limited conversation to collaborators Mar 17, 2024
@glassez
Copy link
Member

glassez commented Mar 17, 2024

Please open new Issue with all the required details.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests