Failed - fail_message is set, but status is Completed

[mastyman]

On some (less common) failed downloads in SAB, where you get messages such as

"unpacking failed, an expected file was not unpacked"
"unpacked failed" unable to find 'examplefilename'.rar"

For example when Sonarr query's this, they get a fail_message is set, but status is "Completed" reply, so Sonarr wont deal with it as its Completed. On most other failures it doesn't come back as Completed, how come for these ones? is it by design?

thanks.

[shypike]

I'll check, but Sonarr does get enough info for this type of problems.

[mastyman]

thanks for looking into it,

FYI i had already logged this with sonarr devs hoping they had enough to work around it, before posting here, but they would prefer it was fixed on sabnzbd side

[mastyman]

hi.. did you have a chance to a look at this? is it something that should be fixed on the sab side or should i keep harassing the sonarr devs to support this alternative type of failure? cheers.

[shypike]

I'll try to get it into release 0.8.0

[mastyman]

thanks, you rock.

[shypike]

Fixed in the source for 0.8.0.
It was definitely a bug.
Because SABnzbd does multiple unpack runs, the second (result-less) unpack
masks the fact that the first one failed.

You can avoid the problem by disabling Config->Special->enable_recursive.
This will disable recursive unpacking, which is rarely needed.

[mastyman]

great thanks for looking into it.