SABnzbd Forums

I've been using SABnzbd for a few weeks now and been having an issue where almost everything that is downloaded fails in one way or another.  Of everything downloaded, I'd say I'm lucky if 10% download properly, pass verification, are extracted and moved to the designated finished folder.  I've been attempting to figure out what the cause is of this and searched the forums and Google without finding a solution.  I've also evaluated the logs and for the most part it seems like the verification portion of SAB is fubared.  I've attempted to replace SAB, restart the system it's running on, changing various settings in the Switches tab to no avail.

I just attempted to try and download something that was just posted to USENET within the past day and have SAB do all automated steps and it fails at verification.  Looking at the logs, it appears that SAB just fails after it can't pass verification and doesn't even try to do a PAR repair and extraction like you would assume be done.  Almost everything that has failed in SAB has been able to be repaired when the PAR2 files were forcibly downloaded and repaired through MacPAR deLuxe.  Has anyone else been experiencing this and is there possibly a way to resolve this?  I really like SABnzbd for what it should be able to do, ie automate my downloads, repairs, extraction, and moving to appropriate folder for Plex to scan and add to library but at this point it seems like SAB is horribly broken and I can't use it for these needs.

For your record, I'm running SABnzbd on OSX 10.6.4 on a 2010 Mac mini with 4GB of DDR3 RAM.  I have my library on a Drobo FS that SAB should move the files to once extracted.  All across a Gigabit network, but I don't have jumbo frames enabled yet, but I don't believe this is related to the Drobo.

Here is the bit of info requested in the Support sticky

Version: 0.5.4
OS: OSX Snow Leopard, 10.6.4
Install-type: OSX Application
Skin (if applicable): Plush though I doubt this is applicable
Firewall Software: None
Are you using IPV6? no
Is the issue reproducible? yes

I've attempted to grab relevant logs for examples and would be happy to post sanitized copies and PM links to the downloads with someone who can assist.  I'd really like to get this resolved.  Thanks!

SABnzbd isn't horribly broken, it runs successfully on thousands of OSX systems.
However it doesn't seem to work on yours.
I can be your system, bad NZB's, odd provider.
It can also be an obscure bug in SABnzbd that happens to surface in your situation.

Please, set logging to Debug and download something using a suspected NZB.
Then collect the log file and send it with the NZB to bugs at sabnzbd.org.

As requested, I've got the associated logs for a download that was just posted to USENET within the past hour and still failed verification.  I've sent an email with the NZB and the associated logs.  Thanks for any help you can provide.

@fanclerks .. remember that even when it is just posted .. this does not eman it is 100% available on your USENET SERVER

NOte that when you have a free server , you will have more problems then when you have a paid one

Well this is through NewsDemon who I thought was one of the more reputable and better providers to have.  Also, you'll notice that these downloads that are failing don't have anything wrong with them. The downloads are complete and most times don't even need the PAR2 to fix anything.  They can be extracted without issue once it's downloaded.  It really does seem like the verification that SAB is doing isn't detecting that everything is right and for some reason doesn't proceed to try and do a PAR2 repair and extraction like you'd assume would be done.

The only anomaly I can see in your logs is that par2-classic is used instead of the multi-core version.
Check your sabnzbd.ini file. Do you find this?
par2_multicore = 0
If so, is there any reason why you disabled the multi-core par2?

It downloads OK on Windows and my old OSX Tiger VMWare image.
BTW: one article is missing (at least it is on my two Usenet providers), so a repair run is actually needed.

Just to eliminate the timing issue.
What happens if you download the NZB you sent me again?

I don't believe I changed that setting as I've only made changes to SAB through the admin panel and not in the ini file.  I'll try to enable it in the ini file, guessing by changing it to a 1?  I actually have the PAR2 settings set to -t0 in Switches tab so I'm not sure as to why the multicore is set to 0.  After that I'll try to download it again and see if I'm still seeing failed verification.  Interesting that you were missing a piece though as mine was fully intact download according to MacPAR.

Well, I've tried and it still fails verification.  This time though it does appear that I got some warnings:

    2010-09-11 15:07:46,974
    WARNING:
    Badly formed yEnc article in

    2010-09-11 15:07:56,730
    WARNING:
    missing

That's all I got.  However, I'd think that SAB should automatically retrieve the appropriate number of PAR2 files and repair the missing pieces but it doesn't appear to have done so.

Badly formed yEnc articles are rare, topic #1047 discusses how they are handled.

It's hard to believe that one badly formed yEnc article would prevent auto-repair.  The warning for it might be unrelated to that issue.

fanclerks wrote: I actually have the PAR2 settings set to -t0 in Switches tab

I don't think the default par2 program we use for OSX supports the -t option!
Even worse, your INI file settings forced the use of par2-classic which certainly doesn't support this option at all.
I think we should actually remove teh par2 options for OSX,
I'll discuss this with our OSX supporter.

Please remove your par2 options.
As long as you have them, every par2 run will fail.
Only 100% correct downloads which pass the "QuickCheck" will succeed.

By removing PAR2 options, do you mean remove the -t0 option or remove parts from the ini file?  I've gone ahead and removed the -t0 from the admin panel portion for PAR2.  Let me know if I need to remove something from the ini.  I hope you don't mean that we can't use PAR2 repair at all on OSX as that doesn't make sense to me since there's a PAR2 that's compatible with it.  I'll try another download and let you know if I'm still seeing failed verifications.

The par2 used for OSX doesn't support extra options, so the field should be empty.

Alright, well I've removed the -t0 like I said above and am downloading something right now.  Will see what happens.  I wonder if that's what caused the apparent skipping of PAR2 repairing of files with a failed verification.

Well, it does appear that the -t0 option was preventing the PAR repairs from happening.  I saw the download fail verification for missing parts and then start the PAR repair.  It says it completed the PAR repair in about 5 minutes and started extracting, but it was some error about a missing .100 part.  I thought that PAR has the files be .1, not .100? Even though it has that error, it still appears to be extracting it though.  I'll update again once done.