Support Forum

Apologies for the delayed reply. This issue just arose, so on second thought, I don't think it's a because of any change to SABnzbd in the recent 0.7.20 update, but rather some quirk of Mac OS X; potentially an update to Yosemite. I've been using 0.7.20 since November when you released it, and this ...

As always, many thanks for the best newsreader out there. I've configured SABnzbd so that all folders it uses are on a secondary volume "Data HD." (I've done this since my main drive is a small SSD and "Data HD" is a larger spinning disk.) Every time the computer restarts and SAB...

Yep. Figured that out. I'm just wondering how the bad RAR files got there in the first place. I've had this set up for years, and this is the first (and so far only) time this issue has arose.

Sorry about the slow reply. Thanks for explaining and for the fix!

Also, the folder uses a * at the end, per "Ending the path with an asterisk * will prevent creation of job folders."

The script doesn't unpack; it just moves and renames. Unpacking is still handled by SABnzbd. The category is set to +Delete, with a folder assignment, and the script.

No. There's a temp folder for incomplete/in-progress downloads/multipart RARs, and then there's a separate "holding" folder for each category. This is where RARs are extracted. Extracted files are moved out of that folder to their final location by the script associated with the category. ...

This past week, I began to receive random "Unusable RAR" errors, and after some troubleshooting, I discovered it had something to do with the category system. The error would only occur with one category I had set up. It turns out that when the destination directory for a particular catego...