Support Forum

Is trunk currently (r2455) stuck in the middle with this? I'm getting/seeing checks for the API key, but no generation of the key anywhere (certainly not on the ConfigGeneral page like 0.4.9, at least). EDIT: Ah, no, I guess for the moment you're killing the check function right before the actual ke...

Also, don't just re-use a filled queue from 0.3.4 with this release. This would possibly explain any issues I had with 779-and-later SVN revisions choking on my pre-779 queue, I'm guessing? Comcast already threatened to cut off my service over excessive downloading in February, how am I supposed to...

Ok, no, that second-to-last one is the most important clue.  How did I miss the "par2 binary... NOT found!" while trying to diagnose a problem with the par2 binary?  SABnzbd's logging even capitalizes the "not" so helpfully, but still I just breezed by. In compiling most of the t...

Some clues, to build up the suspense: It's quite suspicous, because normally one or two INFO lines are logged when par2cmdline does its work. You would see either "all files correct", "repair is required" or something along those lines. Now nothing at all is logged (except the fi...

That is my catharsis post, before I explain what's been going wrong, you see.

http://img.photobucket.com/albums/v472/Bob511/smilies/icon_wall.gif http://img.photobucket.com/albums/v472/Bob511/smilies/icon_wall.gif http://img.photobucket.com/albums/v472/Bob511/smilies/icon_wall.gif http://img.photobucket.com/albums/v472/Bob511/smilies/icon_wall.gif http://img.photobucket.com/...

So far the only scenario that may explain things is when the first PAR2 file is so damaged that no useful information comes back from par2cmdline. But looking at the code, SABnzbd should even recover from this situation. And that doesn't explain why a manual run of par2cmdline on the very same PAR2...

Yeah, my luck.  Thanks for going to such great lengths on my account, though.

If I'm reading things right, it looks like you changed nothing at all in the PAR2 section from the 0.2.5 newsunpack.py to 0.3.1, yes?

I got all excited, because your problems installing a reasonably up-to-date version of python reminded me that I had (in order to not break anything in CC proper) installed 2.5 to /usr/local/bin/python2.5, and redirected SABnzbd.py there--without thinking to change the reference of any of the sub-sc...

I'm going to feel like such an ass when you go through this heroic effort and it turns out to be some dumb, piddling oversight on my part.  :-[ I'm still struck by how--at least superficially--similar my issue seems to the guy's over in the "CRC Failed" thread, with the whole "par ver...

I suppose my next step should be setting back up a pre-plus version to make sure my memory isn't failing on that count. Three hours later, and for that same download 2008-02-17 08:54:55 File.nzb True Stage Par2     [PAR-INFO] smallerfile.mkv: => Verified in 3.8s, all files correct     [PAR-INFO] fi...

- Does it go wrong for every download? - Does it go wrong for every download that has par2 errors? Many downloads unpack without issue; however, my history (sitting at around 388GB worth) does not show a single instance where a repair explicitly took place (simply the [PAR-INFO] "scanning"...

[user]# par2verify file.vol000+01.PAR2 par2cmdline version 0.4, Copyright (C) 2003 Peter Brian Clements. par2cmdline comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it and/or modify it under the terms of the GNU General Public License as published by th...

Looking through the logs some more, it does seem awfully similar to the PAR problem you're dealing with in the other thread; inevitably there's a "::INFO::[newsunpack] Par verify failed on /path/to/SABnzbd/Incomplete/File/file.vol000+01.PAR2!" message in there, but no further par2s are fet...

I was trying to narrow the download session down to a single failed download, so you wouldn't have to hunt through logs of unrelated stuff, but I'll clear out the logs and run a sample download that I'm pretty sure will fail. Running ClarkConnect 4.2 (an RHEL4 derivative), kernel's 2.6.18-8.1.14.3.c...