Page 1 of 1

SAB doesnt grab all PAR2 Files and Fails

Posted: June 26th, 2011, 2:03 pm
by Bydgoszcz
Version: 0.6.5
OS: unRaid
Install-type: Python Source
Skin (if applicable): Plush
Firewall Software: None
Are you using IPV6? No
Is the issue reproducible? Yes

As the subject says, after it finishes downloading it fails without attempting to repair the download even though it is possible to repair. When I check the directory of the finished download that SAB produced it only shows 2 of the 13 available PAR2 files. If I manually download the PAR2 files and attempt to repair the failed download using Mac PAR deluxe it repairs and extracts it just fine, this has happened with numerous NZB's now.

I've tried having various switches enabled and disabled under post processing with no change, the only real difference is having "Post-Process only verified jobs" all that does is fail right after the download, and allows me to retry with out it actually doing anything, even if I grab an extra NZB with the just the PAR2 files and add it to the retry prompt.

Any help would be appreciated, thanks.

Re: SAB doesnt grab all PAR2 Files and Fails

Posted: June 26th, 2011, 3:22 pm
by shypike
Possible the par2 files are oddly named and SABnzbd doesn't get that they belong to the set.
Please email the NZB to bugs at sabnzbd.org (refer to the URL of this thread).

Re: SAB doesnt grab all PAR2 Files and Fails

Posted: June 26th, 2011, 3:42 pm
by Bydgoszcz
Hmmm I might have solved the problem. To run Sabnzbd properly on unRAID I have to install the dependencies. I was running 2.0 and found that there is a 2.1 version.

http://lime-technology.com/forum/http:/ ... 274#p30274

I downloaded the new dependencies from the above link and rebooted the whole unRAID setup, hit retry on a couple failed jobs and they started to repair and extract!
According to the above link the difference between 2.0 and 2.1 is that it updated par2 to the 20090203 32bit release. Which fixes the failed small par2 repair issue. So I guess there was an issue with the par2 were it was just failing to fail.

If the problem does pop again and this little update didn't fix the problem I'll send you an NZB that is failing.

Thanks for the quick reply.