SOLVED: PAR2 options are incorrect SABnzb 0.7.9

[ekpyrosis]

Hi,

I have recently updated SABnzbd to 0.7.9 on my NAS Synology 412+ (multicore) and now I am getting messages like:
PAR2 Options are incorrect, please check settings ->options

When I go there I notice the "Allow MultiCore Par2" is greyed out. (not able to check the check box)

Please advice

Kind regards,

Marc

[sander]

I would do this:

Set SABnzbd's logging to DEBUG. Then run a download again. After the download, and the error message, find lines with "Running unrar" in the log file. Here's an example:

Code: Select all

2013-01-03 23:53:30,386::DEBUG::[newsunpack:563] Running unrar ['/usr/bin/unrar', 'x', '-idp', '-tsm-', '-o-', '-or', '-p-', '/home/sander/Downloads/incomplete/...

So there you see the options that are used by SABnzbd for unrar.

Then login on your Synlogoy, and run

Code: Select all

unrar | head -5

That will show the unrar version you have.

Post all output here.

[shypike]

Sander's advice is almost correct, just replace unrar with par2.

[sander]

Ouch!

So the commands are:

Code: Select all

grep -i "starting par" sabnzbd.log*

(in the correct directory, or just search for "starting par")

and

Code: Select all

par2 | head -5

HTH

[ekpyrosis]

*1* I notice that in the Tab Special the checkbox "par2_multicore ( aan )" was not checked.
I ticked it and restarted SABnzbd, still the Multicore Par2 in the Post processing tab is grayed out.

*2* After restart the info from Debugging is:

Code: Select all

Starting par2: ['/usr/local/sabnzbd/bin/nice', '-n10', '/usr/local/sabnzbd/bin/par2', 'r', '-t0', '/usr/local/sabnzbd/var/Downloads/incomplete/Workaholics.S03E03.720p.HDTV.x264-IMMERSE/workaholics.s03e03.720p.hdtv.x264-immerse.par2', '/usr/local/sabnzbd/var/Downloads/incomplete/Workaholics.S03E03.720p.HDTV.x264-IMMERSE/workaholics.s03e03.720p.hdtv.x264-immerse*']
2013-01-24 19:19:35,412::DEBUG::[newsunpack:1211] PAR2 output was
Invalid option specified: -t0
par2cmdline version 0.4, Copyright (C) 2003 Peter Brian Clements.
par2cmdline comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it and/or modify
it under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version. See COPYING for details.
Usage:
par2 c(reate) [options] <par2 file> [files] : Create PAR2 files
par2 v(erify) [options] <par2 file> [files] : Verify files using PAR2 file
par2 r(epair) [options] <par2 file> [files] : Repair files using PAR2 files
You may also leave out the "c", "v", and "r" commands by using "parcreate",
"par2verify", or "par2repair" instead.
Options:
-b<n>  : Set the Block-Count
-s<n>  : Set the Block-Size (Don't use both -b and -s)
-r<n>  : Level of Redundancy (%%)
-c<n>  : Recovery block count (Don't use both -r and -c)
-f<n>  : First Recovery-Block-Number
-u     : Uniform recovery file sizes
-l     : Limit size of recovery files (Don't use both -u and -l)
-n<n>  : Number of recovery files (Don't use both -n and -l)
-m<n>  : Memory (in MB) to use
-v [-v]: Be more verbose
-q [-q]: Be more quiet (-q -q gives silence)
--     : Treat all remaining CommandLine as filenames
If you wish to create par2 files for a single source file, you may leave
out the name of the par2 file from the command line.
2013-01-24 19:19:35,412::INFO::[newsunpack:825] Par verify failed on /usr/local/sabnzbd/var/Downloads/incomplete/Workaholics.S03E03.720p.HDTV.x264-IMMERSE/workaholics.s03e03.720p.hdtv.x264-immerse.par2!
2013-01-24 19:19:36,103::

*3* after par2 | head -5 command I get:
-ash: par2: not found
head: `-5' option is obsolete; use `-n 5
Try `head --help' for more information.
But I have Par2 installed otherwise I wouldn't get the message (like stated above)

Code: Select all

par2cmdline version 0.4, Copyright (C) 2003 Peter Brian Clements.
par2cmdline comes with ABSOLUTELY NO WARRANTY.

Please help me out here

[sander]

Looks clear to me: "Invalid option specified: -t0".

In Config -> Switches, find "Extra PAR2 Parameters" ... what does that space say? I guess is "-t0". If so, remove it, save, restart SABnzbd

[ekpyrosis]

Thanks I did, but...from the SABNzbd wiki:
Multi-core PAR2

The Win32 distribution of SABnzbd now comes with a multi-core version of the PAR2 program which will see improvements for those with multi-core processors. For linux or OSX you will need to locate the multi-core versions of par2 yourself, such as this one for linux.
The behaviour of multi-core PAR2 can be influenced by an extra parameter.
This option is only of use to users running the multi-core par2 version, so do not specify the value if you are running the normal (single-core) version of par2.
These are the choices:

-t- : Use it single-core
-t0 : Use multi-core for repairs but not for verify (prevents disk trashing)
-t+ : Always use multi-core


And I never had any issues before with the setting -t0

Cheerz

Marc

[sander]

So ... problem solved?

FWIW:
par2 on your system is not distributed by the SABnzbd creators, but very probably by the package creator, as par2 is in /usr/local/sabnzbd/bin/par2
your par2 has no option -t (see your own log at Options). If you think an older par2 had that option (and thus it was multicore), go back in version or contact the package creator

HTH

[ekpyrosis]

Yes thanks Sander

[forkless]

Something is not fully right with the detection of the used binary. I am running from /opt/bin which has a compiled multithreaded par2 binary. It will work just fine, running multiple threads if I have an incomplete set (it will show it uses the /opt/bin/par2 binary, via the detailed job info and `which par2` also returns /opt/bin/par2). However the Config page in the GUI does not seem to think it's the multithreaded binary. For posterity I changed the par2_multicore option to 1 which does tick the box but the option will remain greyed out.

Just a cosmetic issue altogether as the binary runs -t+ per default, but my OCD expects to be able to tick stuff on/off


Ps. On 0.7.14 at the moment

[jcfp]

Something is not fully right with the detection of the used binary.

There is no such detection. In the windows and mac installers there's both a single and multicore par included (and the option to select one or the other is thus active). On any other system, the 'par2' executable is simply what's available on the PATH. Want multicore? Put in the PATH, replacing the single-core version if necessary.