Support Forum

Ah... well, at any rate.. once again, thanks shypike.. greatly appreciate your assistance!

LJ

Sander - I mentioned to skypike that it started after the unrar 5.01 upgrade off github... so, it's very likely, it's a par2 issue... or at least a combination of the two working together.. lol

LJ

Skypike, I have a FULL debug log now from another one that failed. Here's the PAR2 snipit.. I can dump the whole log to paste bin if you want it? 2014-06-03 10:43:59,428::INFO::[nzbqueue:232] Saving queue 2014-06-03 10:43:59,428::INFO::[__init__:881] Saving data for queue10.sab in C:\Python27\sabnzb...

I went into Queue Repair and hit the ADD button to get it to spin out the debugged errors again. I should note in the meantime - I extracted the original .nzb from the .gz archive, added it manually to sab, then started another download of it... worked fine... I can't figure out why it's working som...

Shypike,

I'll PM you a pastebin.

Thanks for looking into this!

LJ

The line Scanning "\\?\C:\Temp\SHOW\SHOW.vol00+4.par2" looks strange: What is the "\\?\" at the beginning? Yeah, I'm not sure either. I also have more in the debug logs ex: 2014-06-02 23:14:37,017::DEBUG::[newsunpack:1146] Par2-classic = True 2014-06-02 23:14:39,638::DEBUG::[new...

More info from the logs: 2014-06-02 20:24:31,573::INFO::[__init__:532] Backing up C:\Python27\sabnzbd-settings\nzbs\SHOW.nzb.gz 2014-06-02 20:24:31,635::INFO::[__init__:532] Backing up \\?\C:\Temp\SHOW\__ADMIN__\SHOW.nzb.gz 2014-06-02 20:24:31,730::INFO::[__init__:836] \\?\C:\Temp\SHOW\__ADMIN__\__r...

I'm currently running from github sources on develop branch (last commit e6094141a089b849880f997ef2ded3f2ab6be84e - dated May 24th, 2014). I'm having an issue with seemingly random downloads being failed as having "Invalid par2 files, cannot verify or repair" error. If I run multipar and m...

Thanks shypike. You guys always keep up the awesome work on this!

LJ

Shypike,

Thanks for the quick response. I think I answered my own question. I just shut down sab and did a "GIT track master."

It's now reporting 0.7.x as the version and the multi-operations is working again. I'll wait for the next release to try

LJ

Fail on my part then. I guess I should switch to "master" GIT. Is that a simple process to do without losing DB/etc?

LJ

I'm having a weird issue with the development release on GIT: When selecting Multi-Operations, the selection box next to the queue name disappears after a few seconds. Clicking on Multi-Operations to disable it, then clicking on it again to enable, does the same thing. Shows up for a few seconds the...

Skypike:

I just installed Beta 2 over Beta 1. No issues with the service going from 1 to 2. I can still test 0.7.5 --> beta 2 if you want.

At any rate, thanks for quick fixes you devs do!

LJ

lol... I can always go back to 0.7.5 and try it again if you want

I looked at the code change that removed the version check, when checking for an already running instance. Under some circumstances the new code can give unpredictable results. This could explain your issue. I will change the code for 0.7.6Beta2 and PM you as soon as it is available. Awesome, thank...