SABnzbd Forums

After my external disk failed last week I decided to upgrade an aging sabnzbd (4.7, I believe) to the lastest and greatest version. Before, virtually every download succeeded. Since that time, however, all downloads fail. Correction: all extractions fail.

Running MacPar DeLuxe afterwards (this is on a Mac, yes), I get checksum errors on nearly all files.

It's the same hardware, same connection, same provider (tweakdsl.nl -- IMO a very good one), just different sabnzbd. I tried downgrading, but I'm now back on 0.4.7 and I'm still seeing the same results.

Looking at the logs I see numerous messages like this:
2010-07-24 19:58:59,287 WARNING [assembler] missing
2010-07-24 19:58:59,376 WARNING [assembler] missing
2010-07-24 19:59:33,031 WARNING [decoder] => missing from all servers, discarding
2010-07-24 19:59:41,596 WARNING [assembler] missing
2010-07-24 19:59:51,054 WARNING [decoder] => missing from all servers, discarding
2010-07-24 19:59:54,462 WARNING [decoder] => missing from all servers, discarding
2010-07-24 20:00:03,806 WARNING [decoder] => missing from all servers, discarding
2010-07-24 20:00:03,843 WARNING [assembler] missing
2010-07-24 20:00:03,965 WARNING [assembler] missing
2010-07-24 20:00:03,976 WARNING [assembler] missing
2010-07-24 20:01:23,249 WARNING [decoder] => missing from all servers, discarding
2010-07-24 20:01:30,272 WARNING [decoder] => missing from all servers, discarding
2010-07-24 20:01:35,896 WARNING [decoder] => missing from all servers, discarding
2010-07-24 20:01:48,738 WARNING [assembler] missing
2010-07-24 20:01:48,748 WARNING [assembler] missing
2010-07-24 20:01:48,759 WARNING [assembler] missing
2010-07-24 20:01:48,969 WARNING [assembler] missing
2010-07-24 20:01:49,782 WARNING [assembler] missing
2010-07-24 23:10:16,305 WARNING [decoder] => missing from all servers, discarding
2010-07-24 23:10:21,747 WARNING [assembler] missing

Clear enough, I'd say: articles missing, no files. Except that both Unison and Vortex managed to download these files without any problems, using the same NZB.


Any ideas as to what could be causing this?

This is not a CRC issue, so I separated your item.
Did you get warning about duplicate articles in the NZB?
If so, SABnzbd will pick the first one, while other programs may pick the second one.
Duplicate meaning: different articles claiming to represent the same file and part number.

Please email an example of an NZB that downloads reproducibly wrong with SABnzbd and right with the others.
bugs at sabnzbd.org
Please include a reference to this topic.

Items like "1248272720.95808.5@news.astraweb.com" are the unique article identifiers.
They have nothing to do with your Usenet provider, but with the one used by the poster.

About the duplicate articles.
Often NZB files from index sites contain two articles for the same file segment.
This makes the NZB by definition incorrect.
The cause is mostly cross-posting (posting in multiple groups).
SABnzbd can only pick one candidate for each file segment and will always pick the
first one it encounters.
Most of the time this is not a problem, but when it is, it results in incorrect files.
If you have enough par2 files, repairing such files may be possible.

I downloaded the smallest of your NZBs from supernews and found no issues.
Your log file is full of weird errors. It looks like your DNS sometimes fails to resolve addresses.
Also, the log says it's release 0.6.2, but the the logging line numbers don't match
what we released as 0.6.2.

Please upgrade to the latest release 0.6.4 first.

I see that you have a 64bit OS.
On some system par2-64bit multi-core sometimes fails.
There is an option to disable the MultiCore Par2 in Config->Switches.
There's also a "hidden" option to disable 64bit support.
See: http://wiki.sabnzbd.org/configure-special item allow_64bit_tools.

Try with both disabled for a while.