Open cliny opened 2 weeks ago
Can you pls post debug logs
Can you pls post debug logs
1. Switch decluttarr to debug mode (setting LOG_LEVEL: DEBUG) 2. Turn off all remove functions but one where you expect a removal (example: REMOVE_STALLED: True and the rest on False) 3. Let it run until the supposed remove should be trigged 4. Paste the full logs to a pastebin 5. If helpful: Paste a screenshot of qbit and the affected *arr app to a pasteimg
Debug logs here: https://pastebin.com/049mWFpi
Thank you
Thank you.
Quite simple really. Your download has "trackedDownloadState":"downloading"
, and the condition decluttar looks for is
https://github.com/ManiMatter/decluttarr/blob/2ee86d35914d24318b83c0672add7954571c9e0e/src/jobs/remove_failed_imports.py#L21-L23
So the question is.. why doesn't the status read "importPending" or "importFailed"? According to the current status, it seems it's not yet "entirely failed" but yet downloading.
Maybe something you want to raise with the Sonarr/Radarr team? Could be that it's a matter of a wrongly implemented mapping on their end (pure speculation)
I see. I could put this forward to the sonarr team?
Otherwise, I noticed the 'trackedDownloadStatus' has 'warning'. Is it possible to get an option in decluttarr where any failed imports that have a status as 'warning' will trigger a removal, instead of waiting for the 'importPending' or 'importFailed' state, even if stuck on 'downloading'?
That‘d be too broad I‘m afraid. No idea what all the different warnings are (for example: insufficient disk space when importing from disk A to disk B). You Wouldn‘t want to delete from A just because B has insufficient space.
I see. I could put this forward to the sonarr team?
yes, raise it on their github, or discord, or directly contribute with a PR
It looks like the sonarr team have added an addition state:
Once you have the new version installed, pls provide the queue-response from Sonarr.
Once you have the new version installed, pls provide the queue-response from Sonarr.
No worries, I'll do this when I have some time, and report back with the details.
Do you know if radarr will implement this, or if I should raise it with them too?
To my knowledge they port it; but if you want confirmation, you need to ask them ;-)
Hi there,
I have found that failed imports with this message aren't being removed:
"Found matching series via grab history, but release was matched to series by ID. Automatic import is not possible"
Or the radarr equivalent of the message.
I even tried explicitly placing the message in FAILED_IMPORT_MESSAGE_PATTERNS=, to no avail. But otherwise I leave it blank to catch all warnings.
Here is a log:
I'm not sure what I'm doing wrong? I'm using the latest stable "linuxserver" containers for everything (sabnzbd, sonarr, etc), updated daily.
Thanks