Closed duramato closed 5 months ago
When nzbToMedia is set to do the extraction, or when option check_media
is used, the script will make this as failed.
In this case, it appears you are passing the .rar directly to medusa and it is medusa that marks this as failed.
To be able to pass this on to nzbToMedia to mark as failed I'd need to add more output matching from the "SickBeard" returned logging...
But as the postprocessing failed, doesn't this get marked as failed
in SABnzbd already?
I have Sabnzbd only doing the download as i want to have Medusa do the extraction. Medusa only has PostProcessing failing becouse of an invalid rar and is not marking anything as failed, what i was expecting would be for nzbtomedia to mark it as failed, like how it does when a download fails on sabnzbd. On sabnzbd for that download what i see is:
"Medusa only has PostProcessing failing becouse of an invalid rar and is not marking anything as failed"
This sounds like an issue in Medusa... If you set either SABnzbd or nzbToMedia to do the extraction, they would make as failed.
Medusa doesn't mark anything as failed by itself, that's the reason why I'm using nzbtomedia. And IMO when nzbtomedia receives a failed post processing from Medusa should mark as failed. I'm doing the extraction in medusa becouse I found it was extracting and then Medusa was extracting again becouse there where still rar files present.
if you set SABnbzd process to +Delete
this should extract and then delete the .rar files so there would not be .rar files for Medusa to extract.
Likewise, if nzbToMedia is set to extract, this should cleanup the .rar files after successful extraction.
in response to that statement, should I set +delete in sabnzbd categories AND enable extraction in the script, or choose one or the other?