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

Watch folder broken in 4.3.5 or later #15127

Closed
1 of 6 tasks
tjjh89017 opened this issue Jun 26, 2021 · 33 comments · Fixed by #15137
Closed
1 of 6 tasks

Watch folder broken in 4.3.5 or later #15127

tjjh89017 opened this issue Jun 26, 2021 · 33 comments · Fixed by #15137
Labels

Comments

@tjjh89017
Copy link
Contributor

tjjh89017 commented Jun 26, 2021

Bug report

Checklist

  • I have read the issue reporting section in the contributing guidelines, so I know how to submit a good bug report with the required information
  • I have verified that the issue is not fixed and is reproducible in the latest version
  • (optional but recommended) I have verified that the issue is not fixed and is reproducible in the latest CI build
  • I have checked the frequent/common issues list and searched the issue tracker for similar bug reports (including closed ones) to avoid posting a duplicate
  • This report is not a support request or question, both of which are better suited for either the discussions section, forum, or subreddit. The wiki did not contain a suitable solution either
  • I have pasted/attached the settings file and relevant log(s) in the Attachments section at the bottom of the report. Mandatory: the settings file and at least the most recent log. See this wiki page if you're not sure where to find them.

Description

qBittorrent info and operating system(s)

  • qBittorrent version: (type here)
  • Operating system(s) where the issue occurs: (type here)

If on Linux, libtorrent-rasterbar and Qt versions

  • Qt: nox
  • libtorrent-rasterbar: same as qbittorrent PPA for ubuntu focal

What is the problem

"Watch folder to add torrent"
this feature is broken in 4.3.5 and 4.4.0alpha1
downgrade to 4.3.4, and it works fine.

Detailed steps to reproduce the problem

  1. update to 4.3.5 or later
  2. setup watch folder
  3. put torrent in folder

What is the expected behavior

add torrent and remove torrent from folder

Extra info (if any)

via linuxserver/docker-qbittorrent

Attachments

@thalieht thalieht added the Can't reproduce Issues that cannot be reproduced label Jun 26, 2021
@strumf666
Copy link

strumf666 commented Jun 26, 2021

Works just fine in 4.3.5 for me.

@bitappend
Copy link

bitappend commented Jun 26, 2021

it broke for me too right after i updated. following for a resolution. really bummed as its now causing problems on 2 different servers for me.

@tjjh89017
Copy link
Contributor Author

that is weird

@glassez
Copy link
Member

glassez commented Jun 27, 2021

"Watch folder to add torrent"
this feature is broken in 4.3.5 and 4.4.0alpha1

Would you like to provide some more valuable information about what exactly is happening with it? I just checked it myself and it works fine (I'm using a custom build from the current qBittorrent master, which is now equal to v4.4.0beta1).

@tjjh89017
Copy link
Contributor Author

@glassez unfortunately i don't know how to provide more info
could you please give me some guide to expose more?

for now, torrent files are still placed in folder and qbittorrent still doesn't download those files.
and i use docker to deploy qbittorent with mounting NFS on host and using volume to bind into container

in host
mount -t nfs xxxx:/volume1/bt /nfs
docker run -it -d --network=host -v /nfs:/nfs -e PUID=1000 -e PGID=1000 ghcr.io/linuxserver/qbittorrent

and in qbt webui
i setup /nfs/watch as watched folder

file permission in host and container
/nfs/*
owner = 1026
group = users
-rwxrwxrwx for all files

thanks a lot

@bitappend
Copy link

The issue is present for both .torrent and .magnet files. It simply is not importing the files from the watch folder.

The version of linux I am running is the latest version of mint. Try installing it on a vm, it might be os dependant?

@glassez
Copy link
Member

glassez commented Jun 27, 2021

unfortunately i don't know how to provide more info
could you please give me some guide to expose more?

Is there nothing about watched folders in qBittorrent log?

@tjjh89017
Copy link
Contributor Author

@glassez let me check it and feedback to you

@bitappend if possible, could you also check log for @glassez in your environment?
thanks a lot

@tjjh89017
Copy link
Contributor Author

(N) 2021-06-28T00:53:44 - WebAPI 登入成功。IP:::ffff:172.29.0.102 (login success info)
(N) 2021-06-28T00:53:59 - Web UI:正在監聽 IP:*,連接埠:8080 (listen on 8080 port)
(N) 2021-06-28T00:54:37 - Web UI:正在監聽 IP:*,連接埠:8080 (listen on 8080 port)
(N) 2021-06-28T00:54:37 - Watching folder: "/nfs/watch"

i used tail -f to monitor the log file
but i only get those logs when i add a folder into watching list and put torrent into folder.
nothing else come out.

@tjjh89017
Copy link
Contributor Author

in watched_folders.json

{
   "/nfs/watch": {
       "add_torrent_params": {
           "category": "",
           "download_limit": -1,
           "operating_mode": "AutoManaged",
           "ratio_limit": -2,
           "save_path": "",
           "seeding_time_limit": -2,
           "tags": [
           ],
           "upload_limit": -1
       },
       "recursive": false
   }
}

@glassez
Copy link
Member

glassez commented Jun 28, 2021

@tjjh89017
Well, I think I found a bug in the code.
To confirm that this is exactly it, and not some other issue, could you enable recursive mode for the watched folder? Current WebUI doesn't allow you to do this, but you could manually modify watched_folders.json file.

@tjjh89017
Copy link
Contributor Author

setup recursive to true
and restart qbittorrent
but nothing happened
no logs from tail -f
torrents are still there

thanks a lot

{
    "/nfs/watch": {
        "add_torrent_params": {
            "category": "",
            "download_limit": -1,
            "operating_mode": "AutoManaged",
            "ratio_limit": -2,
            "save_path": "",
            "seeding_time_limit": -2,
            "tags": [
            ],
            "upload_limit": -1
        },
        "recursive": true
    }
}

@glassez
Copy link
Member

glassez commented Jun 28, 2021

Okay. Everything is fine. The question is whether you can test the corrected version. Do you use only official releases? Or some kind of "nightly" builds, etc.?

@tjjh89017
Copy link
Contributor Author

nightly is ok
but i prefer to use docker and i used arm64 machine
so if you can provide the patch, and i will try to create a container to test

or if this problem will occur on windows
i can use windows to test and you just give a static link executable file to me to test?

tks

@jaxjexjox
Copy link

The watch folder has just broken for me and I have no idea why. Been on qbit now for 3 or 4 years and I'm finally semi-experienced in linux.

Running through docker, latest build: Monday 28/June @ 06:00pm
qBittorrent v4.3.6 Web UI (64-bit)
https://i.imgur.com/CMCwN2L.png
https://i.imgur.com/l9EQ9e9.png

Nothing has changed for me at home, I've been executing it the same way for 12 months.

@jaxjexjox
Copy link

Okay. Everything is fine. The question is whether you can test the corrected version. Do you use only official releases? Or some kind of "nightly" builds, etc.?

I have also done as per request, edited watched folders json - no luck.

@bitappend
Copy link

i updated to 4.3.6 still no dice

@jaxjexjox
Copy link

4.3.6 is no good, correct.

@thalieht thalieht removed the Can't reproduce Issues that cannot be reproduced label Jun 28, 2021
@ForestQ
Copy link

ForestQ commented Jun 28, 2021

I confirm. After upgrading from 4.3.5 to 4.3.6, the watch folder stopped picking up *.torrent

@jaxjexjox
Copy link

I attempted diagnosing this last night and tried pulling in older docker images, however the new 4.4 alpha (which I accidentally pulled in) successfully destroyed my config file, or rather, mad some small dumb changes to it.

Just FYI to the developers - 4.4 alpha, once you pull and run the image, will destroy / remove the watched folder entries in qbittorrent, making them disapear, they'll require re-adding.

Note: this is presumably, seperate from the issue listed here, though quite similar.

@Chocobo1
Copy link
Member

For those affected, please try and confirm the nightly builds (of PR #15137) here:
https://github.com/qbittorrent/qBittorrent/actions/runs/978850405

@jaxjexjox
Copy link

Can I pull it in a docker form from here?
https://hub.docker.com/r/linuxserver/qbittorrent/tags?page=1&ordering=last_updated

I'll happily test.

@Taipan24
Copy link

Taipan24 commented Jun 29, 2021

Win 10, QB watch folder stopped working on 4.3.6 for UNC folder path only. Works well for local watch folder.
Tried also the Recursive Mode, and no dice.

@FranciscoPombal
Copy link
Member

Test builds with the proposed fix for this issue are available here: https://github.com/qbittorrent/qBittorrent/pull/15137/checks (click the links under the "Artifacts" drop-down menu on the right). Please test it.

@tjjh89017
Copy link
Contributor Author

I will test it in few days
Thanks a lot

@Taipan24
Copy link

The issue I reported (UNC path watch folder not working in 4.3.6) is solved in the Windows-x64 test build.

@glassez
Copy link
Member

glassez commented Jun 30, 2021

The issue I reported (UNC path watch folder not working in 4.3.6) is solved in the Windows-x64 test build.

Can you provide example of such path that was affected by this bug?
I tried to make some folder shared and set it as watched folder but it was not affected.

@Taipan24
Copy link

Taipan24 commented Jun 30, 2021

This path didn't work for me in v4.3.6:
\\junol\P2P\Downloads\

@tjjh89017
Copy link
Contributor Author

i found i cannot test nightly build
because i have only arm64 machine
sorry
need other's help to test it

@jaxjexjox
Copy link

I don't know how to 'roll my own' docker image based on source, I probably should learn this but a little busy right now.
If someone knows a very quick guide on how to do it though, I'll give it a shot.

(I don't run it native, always via a simple docker image)

@BradCOnGitHub
Copy link

Should we expect a 4.3.7 any time soon for this?

@jaxjexjox
Copy link

The latest docker container is at least fixed, it's working again for me.

@qbittorrent qbittorrent locked as resolved and limited conversation to collaborators Jul 12, 2021
@glassez
Copy link
Member

glassez commented Jul 14, 2021

Should we expect a 4.3.7 any time soon for this?

I asked the project maintainer to release a new version. But I can't say when it will be released.

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

Successfully merging a pull request may close this issue.