SABnzbd Forums

Hello all, this is my first time posting (I've lurked before). I am trying to learn how to interpret these logs so I can be self sufficient, but I am just getting into it really. I saw the error mentioned in the title today, and when I dug into the sabnzbd log I saw this:

2014-06-08 17:07:04,703::ERROR::[newsunpack:876] Error [Error 87] The parameter is incorrect while running par2_repair on set 59e8ec484ed2b56b9b49b0a2b4f40ad9
2014-06-08 17:07:04,717::INFO::[newsunpack:877] Traceback:
Traceback (most recent call last):
File "sabnzbd\newsunpack.pyo", line 854, in par2_repair
File "sabnzbd\newsunpack.pyo", line 1280, in PAR_Verify
WindowsError: [Error 87] The parameter is incorrect

As I am no python programmer, I thought I'd ask someone here to see what those lines contain, and whether this is a bug or something wrong with my download (much more likely the latter). I'd just go download again, however it is a fairly large data set that I'd prefer to try to fix first.

Thanks in advance for the help!


EDIT: So I am guessing that I need to supply more info to this post since it specifies a parameter being incorrect and that it is in the unpack code. Does the parameter referred to here exist in the nzb file itself?

Check Config->Switches for the extra par2 parameters.
Make sure it's empty.

shypike wrote:Check Config->Switches for the extra par2 parameters.
Make sure it's empty.

Thank you for your response. It is indeed empty.

gaber wrote:EDIT: So I am guessing that I need to supply more info to this post since it specifies a parameter being incorrect and that it is in the unpack code. Does the parameter referred to here exist in the nzb file itself?

Try debug logging (see status page or command line param '--logging 2'), that should show all parameters sent to subprocesses such a par2.

Thank you for the response jcfp. I am indeed using debug logging already - where will I see the subprocesses?

Code says this: So search for "Starting par2" in the debug log of any job that gives you that repair error to find the relevant line(s).

jcfp wrote:Code says this:

Code: Select all

logging.debug('Starting par2: %s', command)

So search for "Starting par2" in the debug log of any job that gives you that repair error to find the relevant line(s).

Right - so that is the original error I posted that found after the par2 process starts:

2014-06-08 17:07:04,703::ERROR::[newsunpack:876] Error [Error 87] The parameter is incorrect while running par2_repair on set 59e8ec484ed2b56b9b49b0a2b4f40ad9
2014-06-08 17:07:04,717::INFO::[newsunpack:877] Traceback:
Traceback (most recent call last):
File "sabnzbd\newsunpack.pyo", line 854, in par2_repair
File "sabnzbd\newsunpack.pyo", line 1280, in PAR_Verify
WindowsError: [Error 87] The parameter is incorrect


Or am I looking for something else?

As I said, a debug log. And the excerpt you posted in the topic start isn't from one of those.

jcfp wrote:As I said, a debug log. And the excerpt you posted in the topic start isn't from one of those.

Fair enough - though I don't see where it puts the debug log. It is not in that same directory.

You can download the logfile from the Status page, where you also set the level to "Debug".

Ok, so the debug line shows:

Starting par2: ['C:\\Program Files\\SABnzbd\\win\\par2\\par2.exe', 'r', <then all of the file names>

The next line is the Error:

Error [Error 87] The parameter is incorrect while running par2_repair on set <GUID>

Can you email the actual content of the log file?
bugs@sabnzbd.org and please include the URL of this message.

Done. Thanks.

What is sent to par2 is an awful lot, that should not be the case.
I can imagine that the Error 87 is caused by an overload of filenames.
Can you also email me the original NZB file?

Sent.