SABnzbd Forums

Blocks grabbed by Sab:

I took an incomplete file and run through NZBOMaticPlus.
Blocks grabbed by NOMP:


Sab grabbed 198, NOMP grabbed 199.

Windows 7 Ultimate x64 SP1
Sab 0.6.5
Astraweb

Thanks for fixing.

How is this setting?
Config->General->"Fail on yEnc CRC Errors"
It may make all the difference.
We've had more reports of trouble involving the combination of SABnzbd and Astraweb.
So far, we're blaming Astraweb, but of course it might be more subtle.

shypike wrote:How is this setting?
Config->General->"Fail on yEnc CRC Errors"

No such setting here.
I have Config>Switches->Post processing->"Fail on yEnc CRC Errors"; "When article has a CRC error, try to get it from another server. "
This setting is off.

I wonder if these import warning issues have anything to do with it.
The corruptions would explain all the failed downloads..

Very likely they do.
It's a sign that something is wrong on your system (or some bug in SABnzbd).
Anything useful in the log file?

Not much, a lot of these:

Same problem here, with Sabnzbd + Astraweb.
The "Fail on yEnc CRC Errors" box is ticked off.
The download through Sabnzbd failed with 17 missing blocks. I retried with other nzbs and got 4 more blocks, but still failing with 13 blocks missing.
Alt.binz downloaded the file without even needing repair.

I'd be happy to provide more info, but I don't see anything relevant in the log, only INFO related informations.

Can you email the NZB file to bugs at sabnzbd.org ?
(Please include this url.)

Ugh, I can't reproduce the bug.
First, I downloaded two files that failed with Sabnzbd. Both were loaded from Nzbmatrix through Nzbdstatus (edit: I got it wrong, it was SABconnect++ on chrome).
Then, I downloaded again the same files with Alt.binz, through binsearch with their integrated search feature. It completed successfully.

To reproduce the bug, I downloaded the nzbs from Nzbmatrix and fed them to Sabnzbd: both downloads completed successfully. WTF ?

So I guess the problem is not Sabnzbd or Astraweb, but probably Nzbmatrix or Nzbdstatus (edit: again wrong, SABconnect++).
I don't know what to think, and sorry for posting before I could reproduce the bug.

So, I finally got my story straight: I didn't use Nzbdstatus on Firefox, but Sabconnect++ on chrome. (I use nzbdstatus to manage sabnzbd on my PC, and SABconnect++ to manage sabnzbd on my mac mini from my PC)
And with this, I got the error again !!! Whoooeeeyy! (kind of).

So:
PC: Nzbdstatus + nzbmatrix: OK
PC: NZB + Nzbmatrix: OK
MAC: SABconnect++ + Nzbmatrix: missing parts
MAC: NZB + Nzbmatrix : missing parts

So, I'm going to have to look further for the cause of the problem.

Alright, I upgraded to Sabnzbd beta 0.6.6 beta2, same problem. I'm using 10.6.7 on a mac mini 2010.
What kind of test can I make to figure out what's the problem ?

I'm emailing the nzb right now.

Just tested on a mid-2010 miniMac with OSX 10.6.8.
Ran it twice, once with "drop articles with CRC errors" on and once off.
Even using Astraweb, like the OP.
No problem whatsoever.

Is the problem persistent for this NZB?
Which Usenet provider do you have?
Could you try again and set the logging level to "Debug"?
Should it happen again, can you email the log file?
(Logging setting on the "Status" page).

Yes, the issue is persistent for this NZB and nzbmatrix link too (I downloaded the file multiple times, it always fails).
My Usenet provider is Astraweb (unlimited, SSL, General servers)

Sabnzbd 0.6.5 & 0.6.6 b2
Mac mini 2010, 10.6.7
OSX .app
Plush
No firewall
No IPV6
Persistent issue

I'm e-mailing the log right now.

Shypike solved my problem by e-mail!
The problem came from the setting "ignore samples" (Config>switches) being set to "Do not download". After I switched it to "off", the file downloaded perfectly fine!

Rock on!
Thanks, Shypike!

This is a nasty one.
The sample files are removed before download, that's OK.
However there's a par2 file called blaba-OTHER.par2 that is used to verify the sample files.
Obviously, that file is not deleted, because it doesn't contain the word "sample" and it
should not be deleted because it verifies more than just the sample.
In the end SABnzbd sees that this is an NZB with multiple parts of which one part doesn't verify.
Subsequently it refuses to post-process any further.
We never found a good way of handling NZBs with multiple parts where one part fails.
We're still thinking about auto-splitting, but in this case, even that might not have helped.
Also, sometimes multiple parts do have a relationship.

Using the "do not download" option for samples is a bit risky.
Maybe we should remove it, because it can go wrong and it's very hard to make it
clear to the user where to look for a solution when it does go wrong.