-
Notifications
You must be signed in to change notification settings - Fork 23
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
Not removing any torrents #56
Comments
IGNORE_PRIVATE_TRACKERS=True could that be it? |
I don't have/use any private trackers though. |
Wait is that referring to indexers? I don't use any private indexers. |
Just re-deployed with IGNORE_PRIVATE_TRACKERS=False and changed the timer to 2 and after 4 checks it still did not remove any torrents. So it's not that setting.... |
Can you please will take a look later thx |
_radarr-decluttarr_logs (2).txt version: "3.3" |
What I find interesting is that the logs suggest that all your torrents are labelled as "Don't Kill", which per your qBit screenshot is not the case. Not sure what's going on. Do you have any idea why this could be happening? Do you have any special setup potentially with your network configuration or so that could be causing this? |
No, I have no idea. The tag is created but i have not set the tag on any of the torrents myself. |
ok, we'll need to investigate that. i'll try to find time on the weekend to create a dev version that could help us going to the bottom of this; would you be ok to help me a bit with back & forth of sharing the logs what's then going on? |
Sure, I'll help with what ever you need. |
Any reason you dont run decluttarr on vm A? Would it work if you did? |
No, I suppose I can. I will try it. |
|
Loggin forbidden is what you get after too many bad attempts; qbit blocks the ip of deckuttarr. pw / username of qbit correct? if on the same network, you can disable login for local connections on qbit as a remedy, too to unblock i think you need to restart qbit container |
Ok, got qbit to connect again, had to change from using IP address to using my domain address and restarted qbit container. But it's still is not removing the torrents... Tested with UFW enabled and disabled. No change.... |
Ok lets leave it as it is and try to find the cause on the weekend… can you try one thing pls: go to radarr/queue and remove the affected torrent there (and ban the torrent). Does it work? because that is what the script does.. |
I've just pushed a version to /dev that gives us more granular logs. you can pull the :dev image to get it.
|
Hi, I removed and blocked a stalled torrent from Radarr and it did remove it from qbittorrent successfully. I will pull the dev image now. |
Ok, I have a dozzle instance that I don't mind opening for sharing my logs for this purpose. you can go to https://logs.myrealm.site to view real time logs and download the logs as well if needed. |
Thx; did you try this? |
Thx apols missed your reply on this. Will check the logs later |
Just checked out the dozzle logs. Unfortunately I can't go back all the way, only the more recent logs seem to be displayed. Would you mind just restarting dozzle, and once the cleaning has been executed that supposedly should remove the movie stop decluttar once again and post the logs? Will then have a look the "traditional way". Cheers and thanks for your help |
Are you wanting to see the logs at the start of decluttarr? [DEBUG]: Using selector: EpollSelector |
I can see where the issue is, but I have no clue what causes it. Check this out: This returns a massive list right now, but the list is wrong. It is supposed to be filtered by those downloads that are tagged with "Don't Kill", but they are included in the response eventhough they are not tagged. It is as if the "tag" parameter was completely ignored as it happens with parameters unknown to qbit. I just tested the corresponding URL on my own setup; works perfectly. So for some reason, in your setup the "?tag=Don%27t+Kill" is ignored. Any ideas why that could be the case? We need to get that fixed, else everything will be marked as "protected" in your case and hence nothing is removed. for reference - here's the relevant documentation for the qbit API:
|
Sorry, but I'm not an api expert. I have no clue either. |
There is a difference in the qbittorrent versions. You are running a newer version than me probably. |
I have qbittorrent version: 4.3.8 |
I have changed to the following and restarted decluttarr. |
Looks like that resolved it! it just removed the torrents it went from 200+ down to 60~ and then Radarr searched other sources and added some more. |
So in conclusion we now know that Decluttarr does not work with qbittorrent version 4.3.8. Add that to your repo for others. Thank you so much for taking the time to look at this with me. |
I'm going to turn on the other options now and let it check and remove all the rest of the torrents. |
Alright well I'm happy with that. If you don't have anything else then I'll switch back over to latest branch and we can mark this resolved. I'm going to upgrade my Sonarr qbittorrent instance and get Decluttarr up on it as well. Hope all goes well there. Thanks again. |
No probs thanks for your help Looks to me rather that the version of qbit vpn you used has a problem with get-parameters. glad you found an alternative that works |
Hi again, so I've been running with the below docker compose for 19+hrs. I have 223 torrents in my Radarr queue and Decluttarr still has not removed any of the torrents.
My understanding of this is that this is supposed to loop every 10mins and check for stalled, failed, missing files, orphaned, metadate missing, unmonitored and/or slow torrents and remove and/or block them after 3 checks, which means after 30mins it should have removed the torrents right? I have slow torrents turned off because most of my torrents are slow, less than 100kbs and a lot of those do eventually download.
What am I missing?
Radarr version: 5.3.6.8612
qBittorrent image: markusmcnugen/qbittorrentvpn
_radarr-decluttarr_logs.txt
version: "3.3"
services:
radarr-decluttarr:
image: ghcr.io/manimatter/decluttarr:latest
container_name: radarr-decluttarr
restart: always
environment:
- TZ=America/Chicago
- PUID=1000
- PGID=1000
## General
- LOG_LEVEL=VERBOSE
#- TEST_RUN=True
#- SSL_VERIFICATION=False
## Features
- REMOVE_TIMER=10
- REMOVE_FAILED=True
- REMOVE_METADATA_MISSING=True
- REMOVE_MISSING_FILES=True
- REMOVE_ORPHANS=True
- REMOVE_SLOW=False
- REMOVE_STALLED=True
- REMOVE_UNMONITORED=True
#- MIN_DOWNLOAD_SPEED=100
- PERMITTED_ATTEMPTS=3
- NO_STALLED_REMOVAL_QBIT_TAG=Don't Kill
- IGNORE_PRIVATE_TRACKERS=True
## Radarr
- RADARR_URL=http://192.168.12.123:7878
- RADARR_KEY=7ede388de16047bc826c825b6c70d13b
## qBittorrent
- QBITTORRENT_URL=http://192.168.12.123:8080
- QBITTORRENT_USERNAME=Removed
- QBITTORRENT_PASSWORD=Removed
The text was updated successfully, but these errors were encountered: