SABnzbd Forums

I am running Sickbeard Build 409 with SABnzbd 0.5.6.  I have been having fairly good luck with SABnzbd completing my downloads and successfully running my Sickbeard post-processing script.  I just recently got a CRC error for a show that I downloaded.  I looked through the SABnzbd log and can't really decipher what it is saying.  It does say there was a CRC error.  However, I am able to use 7zip to unpack what was downloaded by SABnzbd manually.  The resulting .mkv file seems to play perfectly.  This seems strange to me and I am wondering whether anybody can give me any ideas.  What is also strange is that I know I have downloaded this exact nzb before without any issues.  I lost it when I formatted and reinstalled windows the other day and I was forced to redownload it.

Here is the log file from SABnzbd:


2010-12-12 18:26:27,869
ERROR:
Duplicate part 2, but different ID-s ([email protected] // [email protected])
2010-12-12 18:26:27,869
ERROR:
Duplicate part 1, but different ID-s ([email protected] // [email protected])
2010-12-12 18:26:29,617
ERROR:
Failed login for server news.supernews.com:563
2010-12-12 18:26:42,970
ERROR:
Duplicate part 1, but different ID-s ([email protected] // [email protected])
2010-12-12 18:26:42,970
ERROR:
Duplicate part 2, but different ID-s ([email protected] // [email protected])
2010-12-12 19:57:17,510
ERROR:
Duplicate part 1, but different ID-s ([email protected] // [email protected])
2010-12-12 19:57:17,510
ERROR:
Duplicate part 2, but different ID-s ([email protected] // [email protected])
2010-12-12 20:28:58,497
WARNING:
ERROR:: CRC failed in ""

I see there is a "failed login" for supernews, but I don't know what that is from.  I have retested my login credentials and everything is fine.  Any help deciphering what is going on would really be appreciated.  I know that I was able to get things working manually, but I would like to know if I am having some other issue that I need to address.

I am running Windows 7 x64.

Thanks again.

The "duplicate" errors are about badly organized NZB files.
Some parts of file have multiple articles, which isn't really possible.
It's usually sloppiness on the part of the indexer site.
The CRC error is just a single malformed article.
This is either no problem at all or corrected by par2.
Does SABnzbd flag the NZB or failed or did you just see the CRC error in the errors/warnings list?
The latter isn't really a problem.

It gets flagged as a fail and it does not unpack the file or run the rest of the post-processing script (move, rename).  I was able to go into the folder marked as "failed" and unpack the .rar file manually using 7zip.  I received no errors and the resulting file seems to be intact and working properly. 

Thanks again for your quick reply.

Jake

Also know that some couriers have been posting files that have been mangled to the point the SABnzbd can't unrar them. Unrar will fail, but with a manual tool it may work.

What does the History entry for that job show as reason for failure?

This is what the history says:


The Walking Dead S01E05 720p WEB DL AAC2 0 H 264 EbP

Loading config from C:\Program Files (x86)\SABnzbd\scripts\autoProcessTV.cfg
Opening URL: http://localhost:8081/home/postprocess/ ... +H+264+EbP
Processing folder D:\My Stuff\Downloads\Usenet\complete\TV\_FAILED_The Walking Dead S01E05 720p WEB DL AAC2 0 H 264 EbP

The directory name indicates it failed to extract, cancelling

There's nothing wrong with the post except that the poster's NZB files were posted twice by some mistake.  The index site included the duplicate file msg-id's in its NZB.  Binsearch warns with red part numbers.

When I loaded the indexer's NZB into a different client, that client just dropped the articles for the duplicate file and didn't load them, avoiding the decoding errors.

Is there a way you can automatically exclude the poster's NZB files from your download?  They are not included in the PAR2 set.  The SFV and NFO files are though.

pobox wrote: When I loaded the indexer's NZB into a different client, that client just dropped the articles for the duplicate file and didn't load them, avoiding the decoding errors.

The other client probably drops the first version of the duplicate article , SABnzbd drop the second one.
It's an arbitrary choice which will give different results in different situations.

Swallace wrote: logs

That doesn't look like anything from the History entry.

I guess I don't know where the history file is.  I just got the same exact error with another file.  Same situation again, CRC error "cannot unpack."  Yet I am able to unpack it just fine with 7zip or winrar.  It seems so strange that Sabnzbd has no trouble with downloading it but struggles unpacking the file when multiple 3rd party programs can unpack it without issue.  There has to be something I can fix here.

If you can point me to the history file I can upload the history from both of these failed files.

Thanks,

Jake

So the duplicate NZB file is unrelated to the CRC error.

If there really are malformed articles or mangled files in a post I would want the log to show me exactly which ones.

The "cannot unpack" CRC errors should not be happening and the failed logins shouldn't be happening either.

You can't even eliminate bad memory unless your troubleshooting finds another culprit.

We include the standard unrar program by RarLabs.
After par2 verification/repair has been done, it's up to the unrar program to unpack.
SABnzbd doesn't unpack on its own.
Please send a sample of a troublesome NZB to bugs at sabnzbd.org