qbittorrent / qBittorrent

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

won't release files of complete torrents; get error messages trying to move or rename files #6832

Closed chuccck closed 3 years ago

chuccck commented 7 years ago

qBittorrent version and Operating System:

3.3.1 Windows 7 x64

What is the problem:

After a torrent has stopped seeding and shows "complete" as the status, qbittorrent won't let go of the file. When I try to move it or rename it, I get the windows error message "the action can't be completed because the file is open in qBitrroent - A Bittorrent Client". I have auto downloads setup with sonarr and this happens 1 out every 5 downloads or so. Sonarr will send the torrent and set its own label. I do have an incomplete folder setup.

What is the expected behavior:

qbitorrent should not be blocking the file and release it once its complete.

ghost commented 7 years ago

Have you tried updating to the latest version of qb?

chuccck commented 7 years ago

I will try that tonight but I have been weary of any versions past 3.3.1 due to the proxy connection timing out and requiring a restart every day or so.

chuccck commented 7 years ago

No luck. The proxy would not connect in the morning but overnight there was on torrent still locked by qbitorrent. I moved back to 3.3.1 and changed the seed ratio to 0.05 from 0 to see if that helped.

EspeeFunsail commented 7 years ago

@chuccck Did setting your seed ratio to 0.05 or installing the newest version help? I'm also getting this problem still.

chuccck commented 7 years ago

No it did not, still happens periodically. After it's compete and locked, if hit start, wait a second and hit pause again the file is free. Anyone know a script I could run to accomplish this after every torrent completes?

On Jun 26, 2017 2:34 PM, "EspeeFunsail" notifications@github.com wrote:

@chuccck https://github.com/chuccck Did setting your seed ratio to 0.05 or installing the newest version help? I'm also getting this problem still.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/qbittorrent/qBittorrent/issues/6832#issuecomment-311159437, or mute the thread https://github.com/notifications/unsubscribe-auth/AQJQ13azyJbZHtF_KAfMYwXIBYAhaNiAks5sIAfegaJpZM4Ni-UM .

tip2tail commented 7 years ago

Hi,

I ended up writing a batch file that killed the qbittorrent.exe process, slept for 10 seconds and then re-launched it. I set this as the option to run when a torrent is completed. Overkill but it worked.

I came here tonight to log this bug. Might actually take a look at fixing it myself...

t2t

EspeeFunsail commented 7 years ago

Any chance you can share a link to your batch file? One question though. If you just kill qbittorrent and relaunch it, when do you let your renamer/copier program run to move your files? Or do you not use such a program?

tip2tail commented 7 years ago

@EspeeFunsail I would love to but I accidentally deleted it - hence coming here to see if I can help fix the problem rather than a workaround.

That said - I will see if I can re-create it just now :)

tip2tail commented 7 years ago

Oh and @EspeeFunsail - the batch file handled that as well, so the process was: 1 - Kill qBT 2 - Sleep 10 seconds 3 - Run rename tool 4 - Restart qBT

EspeeFunsail commented 7 years ago

Ah ok I see. I do agree that it would be better to have a proper fix for this instead of having to restart qbittorrent effectively every time a torrent finishes, but your method is a decent replacement while we figure out how to fix it.

tip2tail commented 7 years ago

@EspeeFunsail and any other interested parties... I have re-created my batch script. I cant assist with setting this up or tailoring this to your own system but I have tried to document it as best I can. I use the filebot AMC script to rename files, so its configured as such. However feel free to strip various sections from this and use as you see fit.

https://gist.github.com/tip2tail/4be77c3b949ab8882ed4eb7df2997600

EspeeFunsail commented 7 years ago

Thanks @tip2tail! I'll check it out. Really appreciate it!

xavier2k6 commented 3 years ago

3.3.1

Thanks for the report, unfortunately it's too old a version now. If you can reproduce this in latest 4.3.3, please create a "new issue"