SABnzbd Forums

Hello all.

I have a NZB that partially downloaded, then complained it couldn't find the next file so it just gave up and the status became 'failed'.

Now I know the server does have the needed files because I'm currently using NewsLeecher to download the missing files and then do the extracting etc.

But it begs the question, why can't Sabnzbd handle this? Shouldn't you be able to 'retry' or something?

Please let me know if I've overlooked something.

SABnzbd's purpose is to to do full automation.
This requires having reliable NZB files (and providers).
Of course occasional accidents happen, most users shrug and try again.

Designing in interactive features requires a lot of effort, so far
we have invested our sparse time in other features.

To do your manual repairs it's quite handy to have QuickPar ready.
(And WinRAR or 7Zip too).

markbastard wrote: Hello all.

I have a NZB that partially downloaded, then complained it couldn't find the next file so it just gave up and the status became 'failed'.

Now I know the server does have the needed files because I'm currently using NewsLeecher to download the missing files and then do the extracting etc.

But it begs the question, why can't Sabnzbd handle this? Shouldn't you be able to 'retry' or something?

Please let me know if I've overlooked something.

this is not normal, you get occasional problems, but 99% of the time SAB does a wonderful job of delivering your downloads to you full unpacked and ready to go.  You were probably just unlucky.

I don't think he's unlucky, it's something I've noticed on my last four downloads (3 TV episodes and 1 movie).  They have all failed, and yet I've used NOMP to download correctly from the exact same server.

Can you come up with facts to support this?
Were any files not downloaded that should have?
The reaction of SABnzbd when not being able to repair is
to download all available par2 files and copy all raw files to the final folder.
If that set of files is repairable, then you can claim SABnzbd should have done the work.

BTW: downloading at a later time can sometimes fix problems.
Usenet servers need time to sync and when you have a very
recent post, the server might not have all articles.
Also: did you use the same NZB? Because search engines also need time.

Its not just You!

Ive downloaded about 1TB files the last month on my NAS, from Usenet@Giganews. The nzb´s are from Newzbin. Only "certified scene", ie checked and not packed in a weird way.

20-30% goes under complete/_FAILED_ in the completed. These can in 95% be fixed by manual parcheck and unrar, sometimes i need to get parfiles again from Giga.
3 out of 100 goes in  Incomplete and can often be fixed by getting the files again from Newzbin in raw mode.

I love the automatic features, rss feeds etc, and that i can run on my NAS, Newsleecher was a serious mem hogger, but 95% of all files were complete, and unpacked without user interaction.

Ps. Im using 0.4.11 (waiting for a easy package), hoping that the final 0,5 will make Sabnzb truly functional

Are you sure you have a proper par2 program running on the NAS?
Have you tried to verify/repair the files with the par2 program on the NAS,
instead of with one on your PC?
SABnzbd is totally dependent on the correct working of par2.
We do not supply par2 (except for Windows and OSX).
Have you checked with the people who created the package?

If he says "scene" then maybe it is the old sample problem. I.e sabnzbd trying to repair or unpack the sample and then failing on the real file because it does no par2 check on that. Happens to me occasionally and i did not figure out a fix, yet.

Could be a problem.
0.5.0 has a "sample" filtering option, which will remove anything that looks like a sample.
The detection rate isn't 100%, obviously.
I'll have a closer look at what happens exactly when one set fails in a collection of par-sets.

I'm still interested in receiving example NZB files that demonstrate this problem.
bugs at sabnzbd.org

You want nzbs on when this happens with 0.4.12 or with 0.5.x beta?

For each release one NZB. Or one NZB that fails for both releases.

shypike wrote: I'll have a closer look at what happens exactly when one set fails in a collection of par-sets.

When the option "Only post-process verified downloads" is set,
then any failed par2-set will stop further post-processing and
all raw files will be moved to the final folder.
If the option is not set, all sets will be unpacked until the first incorrect one is hit.
This will also lead to the raw files being moved to the final folder.

Until we split sets into separate sub-jobs, we cannot handle this much better.
This isn't planned for the near future because there are so many other things to work on.
It's also not an easy feature to implement.