Sonarr not auto-dealing with Sab - Unpacking failed, an expected file was not unpacked

Help & Support
1

Hi. Sonarr 2.0.0.3039 SAB 0.7.20 both on Windows 8.1 64bit

Failed Download Handling: Redownload is Enabled.

have seen this quite a few times, when you get the much less common failure in sabnzbd Unpacking failed, an expected file was not unpacked

Sonarr isnt doing anything automatically when this happens, just sits in activity.

the rar files cant be extracted, so in my opinion i reakon it should just be deleted/blacklisted and another release searched like it does for other failures

Trace logs here: http://hastebin.com/polokavedi.tex first line has the api call from sabnbz with the unpacking failed message

2

SAB didn’t mark the download as failed so to Sonarr it hasn’t failed. I’m not sure why SAB treats it as successful still, maybe its intentional, but regardless Sonarr won’t handle those as failed at this time.

@taloth fail_message is set, but status is Completed - do we want to handle it as failed?

3

i was going through my history to find some more similar examples, but different error message, i believe same problem where the download has failed, but the status is completed, i dont understand why SAB marks them as complete, doesnt seem right, but i think it would be nice if sonarr could work around it.

here is a different but similar one: Unpacking failed, unable to find xxx.rar

and here is the trace api call for it.
http://hastebin.com/riconudika.md

4

@markus101 No, imo this is a problem for sab to fix.

5

FYI ive started a thread here @ sabnzbd about it, if you would like to add your 2cents…

http://forums.sabnzbd.org/viewtopic.php?f=3&t=18838

6

Reply from Skypike “I’ll try to get it into release 0.8.0”

EDIT “Fixed in the source for 0.8.0.”

or for now can avoid the problem by disabling Config->Special->enable_recursive