Files getting locked preventing Plex and Bazarr from reading them

[hukasu]

qBittorrent version and Operating System

qBittorrent v4.1.9.1 over docker using linuxserver.io's image (linuxserver/qbittorrent:4.1.9.99201911190849-6738-0b055d8ubuntu18.04.1-ls53)

What is the problem

Using Sonarr, Bazarr, and Plex, Sonarr is able to hardlink the files from the download directory to the media directory, but Plex and Bazarr are unable to read them giving messages about permission issues, when pausing seeding the files became available again. I also noticed that it's precisely the files being seeded that are getting locked, if the torrent has 10 files, about 4~5 get locked.

What is the expected behavior

Shouldn't qBittorrent open the files for seeding as read only?

Steps to reproduce

Have Sonarr, qBittorrent, and Plex or Bazarr set up on docker, in a way that Sonarr are able to hardlink, download an episode/batch of episodes and leave it seeding, on Plex, it will show as Unavailable when looking at the file info and give "Please check permission" error when trying to playback. And with Bazarr, it's unable to download the subtitles because it can't read the mediainfo.

[kiwicacid]

Hi,

Same problem here with Medusa and Plex.
For the moment I've "resolved" the problem by creating a cron job, every hour the permissions are changed.
But it's cleary not the best solution.
I'm interested if there is a better one.

[hukasu]

@kiwicacid it would be nice of you to include what the version is that you are using, it's been so long that i had this issue that i didn't even remeber that it was still open

[kiwicacid]

Yes, you're right.
It's a brand new install with Debian 10, Medusa 0.4.2 and qbittorrent-nox 4.1.5 ... which I now realise that I don't have the last version of qbittorrent ... how did I do that ...
Still, did you found a solution since last November ?

Sorry for the delay, I didn't see the mail of you reply.

[FranciscoPombal]

@hukasu @kiwicacid

I don't think qBittorrent locks torrent payload files in any way on Linux whether they're being read or written to. The "exclusive write access by default" is more of a Windows thing. This bug might be the result of some limitation of those other programs, or some problem that only occurs when using with Docker, probably because of some missing configuration of it.

I would first try to reproduce the problem with 4.2.5, then with 4.2.5 and outside of Docker. Then we'll go from there.

[kiwicacid]

@FranciscoPombal
Thanks for the answer, I'll try to upgrade to 4.2.5 as soon as I can then come back here to tell the result.
Just one thing, what's a Docker and so, what do you mean about outside the docker ?

[FranciscoPombal]

@kiwicacid

Just one thing, what's a Docker and so, what do you mean about outside the docker ?

It's a containerization technology. If you don't know what it is and don't use it, don't worry about it, that comment was more aimed at @hukasu who is using it.

[hukasu]

@kiwicacid

Just one thing, what's a Docker and so, what do you mean about outside the docker ?

It's a containerization technology. If you don't know what it is and don't use it, don't worry about it, that comment was more aimed at @hukasu who is using it.

it could have been an issue with Docker for Desktop, i have a vague memory of one of it's changelogs mentioning changes to how they handle files
so, maybe close this thread? unless someone is able to replicate it again

[FranciscoPombal]

OK, if someone is able to reproduce with the latest version, please open a new issue.