Better sab & couchpotato/sickbeard integration

[causalloop]

It'd be nice if this was all in one app...

The problem I have is that if sickbeard sends something to sab, and sab has a problem, i.e. the file is out of retention or its missing par files or whatever, it should go back to sickbeard (or couch potato) and do something like, download another version etc until it exhausts its options. Maybe this functionality is already there and I'm just missing something obvious?

[shypike]

Simply disable "Post-Process Only Verified Jobs" in Config->Switches.
And then hope that the script is able to handle the error codes that SABnzbd sends it.

[causalloop]

That didn't seem to change anything. I keep getting: "Download might fail, only 0.0% of required 100.0% available " which I guess is its own issue... but Sickbeard is sending things to sab, sab gets that error and everything just stops. It doesn't check to see if there's anything or any other quality available.

[shypike]

That means you're using the "check before download" option.
That is not very useful for an automated solution, you should disable the option.
You''re then still left with the situation where the download is completely empty.
In that case the script still doesn't run.
That issue will be solved in a later release.

[causalloop]

okay. Thanks for the info.

[clinton hall]

For CouchPotato there is regular api polling of sabnzbd that will trigger the next best release to be downloaded on failure.

Due to some heavy resource loading when trying api calls etc when downloading large movies, this may not work properly. In this case, use my sabToCouchPotato post process script. This script will run the CouchPotatoServer renamer if completed and will request the download of the next best release in failed.

If/when sabnzbd is able to handle execution of the script form"out of retention" (DMCA takedown?) then this will work for that too. Right now the built in api monitoring is the only way to catch these failures (if your system can handle it). The problem is, if sabnzbd takes more than 60 s to respond to an api call, CPS gets no status for the release, assumes it to have been deleted, so sends the next release... Some people end up downloading the same movie successfully 3-4 times! But we are working on a fix... So use the pp script for now if that happens to you.

As far as SickBeard goes. There is no way currently to mark an nzb as "do not download" if you try and search again it usually grabs the same one. So I can't write a script to handle this. There is a branch in GitHub that supports this, and we are waiting to see if this gets merged. But no indication as to the likelihood or the date. Go to SickBeard forums and request this feature.. More people asking means more likely to happen.

@shypike given the increasing frequency of DMCA takedowns, it appears that more people are experiencing these failures. As indicated, api monitoring is not (experimentally) the best method on low power systems (NAS) so postprocessing is in my opinion the way to achieve this. The ability to run scripts for any failure mode would be beneficial, so if you were able to implement this in the next release I for one would be very greatful.

[causalloop]

Okay, I'll give that a go for CP.

Has there been any talk(s) about merging CP, SB, and Sab or are these intentionally separated?

[shypike]

Three completely different teams, each with their own agenda and priorities.
Don't hold you breath.

[causalloop]

well, it was a nice thought ;-)