[ SabNZBdPlus 3 ] [ 4.0.1 ] The automated Usenet download tool

[QNAP_Stephane]

Source https://sabnzbd.org

Downloadx64 , arm64, arm-x41 (removed due sabyenc requiere a newer gcc)

https://www.myqnap.org/product/sabnzbd-plus/ (old version not maintained)

Apache81 : https://www.myqnap.org/product/sabnzbdplus-apache81/
Apache82 : https://www.myqnap.org/product/sabnzbdplus-apache82/

QPKG Integration

Code: Select all

This QPKG run on port 9292 by default HTTP
cross compiled with unrar 5.9.4 and Par2CMD Line (MT) ( https://github.com/jkansanen/par2cmdline-mt )
config file /opt/QSabNZBd3/SAB_CONFIG/config.ini
logs file /opt/QSabNZBd3/SAB_CONFIG/logs

About

Small and large screens
With the responsive Glitter interface, you can access SABnzbd and manage your downloads from any device: desktop, tablet or phone. Others have made Android/iOS (LunaSea), Android (nzb360) and iOS (nzbUnity) apps to manage SABnzbd.

Integrates with other tools
Apps like Sonarr, SickChill, Radarr, Headphones, Lidarr and more can integrate with SABnzbd and automate your download process.
SABnzbd can also read and process RSS feeds, activate custom scripts and notify you.

In 16 languages
SABnzbd now ships with 16 localizations:
English, Dansk, Deutsch, Español (castellano), Français, Nederlands, Norsk bokmål, Polski, Português Brasileiro, Româna, Suomi, Svenska, русский язык, српски, עִבְרִית‎‎, 简体中文.

[GTunney]

Thanks for this Stephane.

Is there any way to transfer config from 2.3.9 to 3?

[QNAP_Stephane]

dont think it is posible.. we move from Python2 to python3 not sure all can be compatible on migration

but both can run aside... i am using a different port and an other name for QPKG V3

[OneCD]

Configs from 2.3.9 work fine in 3.0.0.

[GTunney]

dont think it is posible.. we move from Python2 to python3 not sure all can be compatible on migration

but both can run aside... i am using a different port and an other name for QPKG V3

Copying config from 2.3.9 works.

It's saying I don't have Multicore Par2 installed? I have par2cmdline from Qnap club repo installed but Sab3 isn't detecting it.

[QNAP_Stephane]

it is in QPKG Path which is exported in $PATH on qpkg start

/opt/QSabNZBd3/bin/par2

[GTunney]

it is in QPKG Path which is exported in $PATH on qpkg start

/opt/QSabNZBd3/bin/par2

Yes i have the below in there

par2
par2create
par2verify
par2repair

[GTunney]

I've managed to resolve this.

I checked my old Sab install and noticed par2 was renamed to par2.old presumably so it can use the par2 installed via par2cmdline-MT

Done the same on my new sab and renamed par2 to par2.old, restart sab and it's now detecting multicore par2 via Par2cmdline-MT app.

[Maggus]

Done the same on my new sab and renamed par2 to par2.old, restart sab and it's now detecting multicore par2 via Par2cmdline-MT app.

Thanks, this was the point! Did the same and now multicore is available!

P.S.: Thanks Stephane for your great work! Your next beer is on me, donation is on the way! Cheers!

[stormer]

Hi Stephane,

Please check following topic on SABnzbd forum about multicore par2 on V3.0.0. They suggested to post it here to make you aware.

https://forums.sabnzbd.org/viewtopic.php?f=3&t=24893

Edit: I noticed now it was already reported here.

Kind regards,
Stormer

[pippotaz]

I've tried moving over the config from 2.3.9 to 3.0.1 but after that SabNZBdPlus 3 reports version 2.3.9 (with the old version not running) I've peeked into the config file but can't find a way to correct that....
(if you're wondering restoring the original 3.0.1 config shows the correct version instead)

Also about renaming par2.old where did you find it in the install folder ?

Thank you !

[tanderson92]

I just upgraded to 3.0.1, and now SAB won't start. The config file didn't change from my last update 20 August, but https://nasip:8243 reports unable to connect. Trying to start SAB from the QNAP shortcuts opens http://nasip:9292, which also reports unable to connect. Is there a way to see what port this running server is using?

I wound up just completely uninstalling and reinstalling SAB, keeping a copy of my config file so that I didn't have to re-enter the server names and other configuration. That worked fine, but again the new qpkg is looking for port 9292 instead of 8243, even though the config.ini has 8243 as the port. I'm assuming this has to do with the way the NAS assigns ports to installed applications. Is there a way to force a certain port on a qpkg, or will it just randomly change from time to time as the package is updated? EDIT: the port was a red herring. The configuration has 9292 as the insecure port and 8243 as https; both work fine after the re-install. The issue was something else, not the port.

[Maggus]

I just upgraded to 3.0.1, and now SAB won't start.

I had the same issue. I did a backup from my config and reinstalled it. restored the config, rename the par2 file again and sab did work again. No idea where the issue was...

[QNAP_Stephane]

updated

[QNAP_Stephane]

updated