Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
What I've noticed is if I use SickBeard to download an NZB and pass it to SAB, if I view the contents within SAB as it's downloading, there aren't any PAR2 files in the queue. If I manually import the same NZB and view the contents with the queue for that download, I can see the additional, needed, PAR2 files.
The download just finished from the above example.
After it completed download:
14 X *.rar files
1 X 11kb *.par2
6 X *.volXX+YY.par2 files
it moves the folder and contents from the temporary "incomplete" location to the "completed" folder where normally Sick Beard picks it up, renames it, etc
However, in the completed folder location, now the single 11kb *.par2 file is missing. Somehow it got deleted. (?) The completed folder has:
14 X *.rar files
6 X *.volXX+YY.par2 files
I cannot tell with just this info.
Normally SABnzbd would clean up any used par2 file,
but only if the verification/repair was successful.
Left-over par2 files do not belong to the rar/par set.
Are you letting failed downloads proceed to SickBeard?
I was reading the forum last night and one of the admins told the OP to turn off the sample detection because it was kinda hinky at the moment. So I copied suite and also disabled the sample detection.
awsic wrote:In the log files I see:
/usr/bin/par2: error while loading shared libraries: libtbb.so.2: cannot open shared object file: No such file or directory
added libtbb.so.2 to /usr/bin/, tested via downloading a file I've been looking for and so far, it's working. Will test more overnight.
... to /usr/bin? Why not /usr/lib/? And why not remove & install par2?