Positively sure there is something fishy on Raspberry Pi

[sander]

Does my version take into account this -N option for par2, even with 0.6.14 installed?

You have version 0.6.14 as regular?! That's not good.

No, the git version is not beta3. How did you get the git version?

[sander]

pi@raspberrypi:~ $ cat ~/.sabnzbd/logs/sabnzbd.log | grep "Starting par2" | cut -c-200
2016-01-11 17:54:36,987::DEBUG::[newsunpack:1195] Starting par2: ['/usr/bin/par2', 'r', '/media/usbdrive/50389c8b66cec608eb8081a7/Avengers (2012) HDrip BBer.mkv.par2', '/media/usbdrive/50389c8b66cec60
2016-01-11 19:24:03,511::DEBUG::[newsunpack:1195] Starting par2: ['/usr/local/bin/par2', 'r', '/media/usbdrive/50389c8b66cec608eb8081a7/Avengers (2012) HDrip BBer.mkv.par2', '/media/usbdrive/50389c8b6
pi@raspberrypi:~ $

So here we see the new version of par2 being in use (good).
The folder names behind /media/usbdrive are truncated, but that's probably a log thing?

There is no -N option in your logging, so you have not set it up correctly. But I think the cause is you did NOT get the git version.

[summer10]

Does my version take into account this -N option for par2, even with 0.6.14 installed?

You have version 0.6.14 as regular?! That's not good.

What are you talking about? Of course I have version 0.6.14 as regular. I just did a sudo make install, which installed par2 v0.6.14 in /usr/local/bin, as I said. /usr/local/bin being in the system path, this makes v0.6.14 the system default par.

No, the git version is not beta3. How did you get the git version?

I did not get the git version. When I installed 0.8.0 beta 3, last week, I did it by using an Ubuntu PPA, as mentionned in this forum, which worked fine.

[summer10]

No, wait ... not there yet. Possible ways to go forward:

1) Do a manual "par2 r -N *.par2" in the directory containing your download.

My latest download of the same "test" nzb failed again (86 blocks short this time), so I tried to manually repair, using my freshly installed par2 v0.6.14 (obviously), and here is the outcome:

Code: Select all

There are 1 recoverable files and 0 other files.
The block size used was 768000 bytes.
There are a total of 2485 data blocks.
The total size of the data files is 1907745394 bytes.

Verifying source files:

Target: "Avengers (2012) HDrip BBer.mkv" - missing.

Scanning extra files:


Repair is required.
1 file(s) are missing.
You have 0 out of 2485 data blocks available.
You have 196 recovery blocks available.
Repair is not possible.
You need 2289 more recovery blocks to be able to repair.

What shall I conclude?

[summer10]

pi@raspberrypi:~ $ cat ~/.sabnzbd/logs/sabnzbd.log | grep "Starting par2" | cut -c-200
2016-01-11 17:54:36,987::DEBUG::[newsunpack:1195] Starting par2: ['/usr/bin/par2', 'r', '/media/usbdrive/50389c8b66cec608eb8081a7/Avengers (2012) HDrip BBer.mkv.par2', '/media/usbdrive/50389c8b66cec60
2016-01-11 19:24:03,511::DEBUG::[newsunpack:1195] Starting par2: ['/usr/local/bin/par2', 'r', '/media/usbdrive/50389c8b66cec608eb8081a7/Avengers (2012) HDrip BBer.mkv.par2', '/media/usbdrive/50389c8b6
pi@raspberrypi:~ $

So here we see the new version of par2 being in use (good).
The folder names behind /media/usbdrive are truncated, but that's probably a log thing?

There is no -N option in your logging, so you have not set it up correctly. But I think the cause you did NOT get the git version.

This is correct : I have not installed the git version yet.
Is it worth trying the git version, knowing that manual repair using par2 0.6.14 does not succeed (seems like it: see the message immediately above)?

[sander]

This is correct : I have not installed the git version yet.
Is it worth trying the git version, knowing that manual repair using par2 0.6.14 does not succeed (seems like it: see the message immediately above)?

Yes, it's worth it:
Getting the official SABnzbd git version is easy-peasy:

Code: Select all

sudo apt-get install git
git clone https://github.com/sabnzbd/sabnzbd.git

Done!

Then run it with (first stop any running SABznbd)

Code: Select all

cd sabnzbd
./SABnzbd.py

Fill out -N in par2 options in SABnzbd -> Config -> Switches, and re-download

[summer10]

It works... but! I need to make sure it really, really works reliably - I will retry tomorrow. I will test extensively and report back.

One question before I wrap up for tonight. How do I install SAB as a service from the Git repository? Is there any install procedure from the repo?

I was a bit scared about 2 hours ago: I got SAB off Git then ran it as a regular process (./SABnzbd.py). I looked at the web page... "Retry". I thought "crap...". I don't know what happened, either it really failed (I will be praying it didn't), or my SSH session timed out: the shell was therefore killed, and as a result the SAB process was killed too, being a child process. I believe that if I run SAB in the background (with an '&') this will also happen.

I could install screen to launch true background processes but would like to install SAB properly.

[sander]

One question before I wrap up for tonight. How do I install SAB as a service from the Git repository? Is there any install procedure from the repo?

Not that I know of (FWIW).

However ... as that "set -N manually" fix is now in the SABnzbd git version, it will be in the next release of SABnzbd (0.8.0 Beta5 or real 0.8.0 version, whatever version will be the next). You have activated the PPA for SABnzbd on your Raspi, right?

[summer10]

I tried again this morning, and it worked too. Thanks for your help.
So the current Git version seems to work fine with the -N switch. I will test tonight without the -N switch, to be sure I understand everything

Can you explain why the Windows version worked? Is it because -N is always enabled?

[safihre]

Because it's a much older multi-core version of the program, before any of the 'improvements' made in the new par2cmdline that apparently require now the new -N option..