SABnzbd Forums

Running SABnzbd on OS X Lion, and for every download I get: » PostProcessing was aborted (see logfile)

The log files say nothing, just that it failed.

But, nothing failed. The files are always there and in good working order, and there's a like __FAILED directory.

Why is this happening? What can I do?

Please set the logging level to "debug", try again and email the resulting
log file to bugs at sabnzbd.org
Do you use a user post-processing script?

Well this is the same problem I'm having, and I'd like to get to the bottom of it, even though this guy didn't follow through.

OS X Lion 10.7.2
sabnzbd.app 0.6.10
sickbeard post processing script

The problem started after I upgraded to Lion a few days ago. Since then, most, but not all, downloads result in "PostProcessing was aborted." (Mine aren't resulting in a _FAILED folder, just sitting in the Incomplete folder.) All the files are there; they manually unzip just fine.

I've set my logging level to debug, hitting "Retry" on a failed download, and emailing the resulting log file.

CasualSubversive wrote:"PostProcessing was aborted."

There can be various causes, but only looking at the logs will tell you more.
If you have no final folder, then it's not likely that SABnzbd even got as far as the SB script.

Your log ends with "Queue has finished, launching: None".
You don't have and end-of-queue operation set, do you?
Also, it's not a debug log, so quite a bit is missing.

Well, sickbeard makes the folders, and all of the episodes have been for seasons in progress, so that's not the issue.

I don't have any end-of-queue operation set that I'm aware of, just the standard sickbeard post processing as individual items finish.

I did exactly what you told wellsoliver, I set the Logging dropdown menu on the Warnings page to "+Debug." Then I hit retry on a download with aborted post processing to generate a new log. If that didn't work, how can I get you a debug log to look at?

Zip and email to bugs at sabnzbd.org (add this URL).

You misunderstand, I did that last night. It's the log you looked at.

I didn't spot some things in the log.
It looks like SABnzbd cannot communicate properly with Growl.
We're working on fixing that for 0.6.11 (Growl causes the problem, but SABnzbd doesn't handle it properly).
Can you disable Growl support in Config->Switches and see what that does?

That seems to have done the trick for the two failed downloads I had sitting in the system. I'll post an update if the problem crops up again over the coming week.

As long as I'm talking to someone who's thinking about integration with the new Growl—I'd really like more granular control over the various messages sabnzbd sends through growl. Specifically, with Growl's new logging feature, I'd like to be able to log failed download messages, but not successful download messages. Right now, they share the same setting, so I either have to log both or neither.

0.6.11RC1 is out now which fixes the crash problem.
It won't before 0.7.0 that we will overhaul Growl support.