SABnzbd Forums

Previously, I managed the installation with Sherpa install script on the QNAP, which normally installs the par2 multi-core in the assumption that the chip is multicore.
However, SABnzb indicates in the settings "Par2 Multi-Thread" "Not Available"




So I tried to force this by installing a package Par2cmdline-MT, Last release: 0.6.14-MT, found on the site qnapclub-eu, compatible with the TS-x28a (Proc Realtek quadCore 1295).




However, SABnzb always indicates in the settings "Par2 Multi-Thread" "Not Available".

Should we create a link by a command line, or change a settings ?

wallygator79 wrote: ↑August 17th, 2018, 11:43 am Previously, I managed the installation with Sherpa install script on the QNAP, which normally installs the par2 multi-core in the assumption that the chip is multicore.
However, SABnzb indicates in the settings "Par2 Multi-Thread" "Not Available"

Sorry, there isn't a multi-core Par2 available for QNAPs. The best we can do is the multi-threading version. The sherpa script will choose the appropriate version of Par2 to install.

@OneCDOnly: we also detect par2-Mt, but you say some models it won't work for?
I know par2-tbb can be more difficult, but the Mt version should always work.

safihre wrote: ↑August 18th, 2018, 3:33 am @OneCDOnly: we also detect par2-Mt, but you say some models it won't work for?

I think the problem is that the OP has confused 'multi-core' with 'multi-thread'. The screen-shot of the warning message says multi-core.

The multi-thread Par2 is installed by default unless it's incompatible with the user's NAS model and OS version. In that case, a plain single-thread version is installed.

The OP's NAS supports the multi-thread version, so it would have been installed via sherpa. But - understandably - this doesn't stop the warning regarding the missing 'multi-core' version appearing in SABnzbd.

At present, the package maintainer for the Par2 binary (which incorporates the merged par2cmdline-MT) has not created multi-core versions. It's quite a job - there are 11 different NAS architectures to compile for, but only some of these are multi-core. And he has several hundred other software packages to maintain.

For sabnzbd this error is triggered when we can't detect the -t parameter (or whatever the one is that specifies the number of threads to use).
So in this case he really has the single threaded version.

safihre wrote: ↑August 19th, 2018, 1:41 am For sabnzbd this error is triggered when we can't detect the -t parameter (or whatever the one is that specifies the number of threads to use).

Can you explain how that parameter is detected? I've only ever seen that warning from SAB when I was using a non-multi-core Par2 binary (including multi-thread versions).

I haven't specified a parameter for '-t' on my plain Debian installation that has a multi-core Par2, and SAB shows no warnings about this.

safihre wrote: ↑August 19th, 2018, 1:41 amSo in this case he really has the single threaded version.

Sorry, no.

Both times, the OP has the multi-thread version. Par2 (the updated multi-thread version is 0.7.4.0) is installed by default via sherpa, then the OP manually installed the older Par2cmdline-MT (0.6.14) package where the MT means 'multi-thread'. This can be seen in their App Center screenshot. So, the OP has actually downgraded their config, but it still supports multi-thread.

We call `par2 -h` during startup of Sabnzbd. Then we parse the output to see if the command line help included that threads parameter. It's not dependent on the user settings.

Multi core == multi threaded, there's no difference. I helped with both projects, so I know :p

In that case, I’ll stand-aside and wait for a resolution.

Wallygator: could you login to your NAS using command line and run
par2 -h

And post output here?