SABnzbd Forums

I wasn't able to fine anything on this, but for awhile now I have been having multiple failed downloads but all are repairable with quickpar. It always seems to be the same shows that fail and from different uploaders. I have been using sab for a few years now and this started after nzbsrus went bitcon and all that other stuff happened. Nothing has changed on my configuration, i'm at the latest release of everything, using astraweb. Not sure whats happening or if this is being working on already.

Which version of SABnzbd are you using?

SABnzbd Version: 0.7.11 on Win7 64 bit

Can you email a representative NZB example to bugs@sabnzbd.org ?
(Please add the URL of this post to the email.)

One of the downloads that fail?

sirwankel wrote:One of the downloads that fail?

Of course.

I only have one right now to send. I will have more tonight or tomorrow night. Thank you

No problems here with the NZB you sent, even when deliberately damaging part of it.
It's just a run-of-the-mill NZB, using the proper naming convention.
Which operating system are you using and if not Windows/OSX, where does your par2 program come from?

i'm using windows 7 64bit and to manually repair them in using quickpar. I know someone else locally who is having the same issue. We are both using Win7 64, same server service, same internet service, only thing that is different is our hardware.

The only thing that may help me find a cause is to create
a debug log of such a download (see Status page).
BTW: do all par2 files get downloaded?

I will send the debug log when I get home. I believe they are, that's what quick par uses to repair the file. The seem like quick repairs when it repairs them. Some don't even need repaired per quick par. I have noticed that it says 1 file needed when it's done but it extracts fine. Seems like it is saying there are 101% of the files needed

sirwankel wrote:Seems like it is saying there are 101% of the files needed

Are you using the "check before download" option?
That option is just there for people who don't want to take risk of downloading stuff that may turn out unrepairable, but it's not a fully reliable prediction.
You can overrule the prediction by using "Retry" from the "failed" History entry.

I did have "check before download" selected. I turned it off, will let you know how it goes