SABnzbd Forums

Currently on version 0.7.6 on Windows 7 x64

For some reason I seem to be getting some nzbs that are just failing. From the download screen the status is just "failed".

When I go to the files that are left on the system they always work when I got to unrar them. No need to fix them at all, just right click and extract to directory and they come out great.

Here is a link to the logs. Hopefully someone has some insight into why they might be failing.



Is there another log that I should be looking at? Is there a way to turn on more verbose logging?

If you look towards the end there is two 2 broke girls from 12/11, Mentalist from 12/9 and Nikita from 12/7

Here are my Post Processing settings



Thanks for the help

Josh

First hypothesis: a post-processing script (SB?) that returns a fail-value. So: test without any post-processing script.

Interesting idea. They all use the exact same post processing though.

Oh wait: do you mean the "[newsunpack:823] Par verify failed on" ?

If so:
Don't you see "Par verify failed" in the SAB GUI?
What if you turn off MultiCore Par2? And remove the extra parameter?
Can you run a manual par / par2 verify on the file and see what happens?

I don't see anything about Par Verify Failed in the GUi.


Am I missing something?

I could try turning off multicore par2 but I have reservations about it. 90% of things work, it's just these few every week that error out. What would make most of them work and some not? As far as I can see there are no errors with the files when unrarred manually. They are misnamed though. I've noticed that if I do run them through quickpar it renames them but should I be able to do the same thing within SAB?

Set logging to Debug on the Status page.
Then after such a failure look at the end of the log file for more clues.
(Log file also available from the Status page.)

Thanks.. I'll look at that

sander wrote:Oh wait: do you mean the "[newsunpack:823] Par verify failed on" ?

If so:
Don't you see "Par verify failed" in the SAB GUI?
What if you turn off MultiCore Par2? And remove the extra parameter?
Can you run a manual par / par2 verify on the file and see what happens?

I won't doubt you again. It looks like it was erroring out with the -t1 , I changed it to -t+ and no errors. We'll see how it goes.

Thank You