Page 1 of 1

Getting stuck at unrar stage

Posted: September 28th, 2010, 8:56 pm
by grog
I've been running 0.5.3 on Windows 7 64-bit for a couple of months without issues but all of a sudden a strange problem started happening this past Sunday night. My downloads are now getting stuck at the unrar stage. The status in the history shows "Repair: Quick Checking" but it stays there for hours and the sabnzbd process shoots to 100%. There is also an unrar process still running and if I kill that it will then proceed to the moving stage and then fails with the message "Unpacking failed, [Error 299] Only part of a ReadProcessMemory or WriteProcessMemory request was completed".

I tried restarting sabnzbd first, then rebooting, but the problem still occurred with subsequent downloads. I then cleared the queue and upgraded to 0.5.4 which I'd been meaning to anyway but that didn't help either. I also tried starting it with the --clean option but still the same problem.

Has anyone else seen this?

Re: Getting stuck at unrar stage

Posted: September 29th, 2010, 1:53 am
by shypike
Very occasionally we get a report like this.
It seems that on some systems the 64bit version of unrar doesn't work.
Disable 64bit tools, as described here:
http://wiki.sabnzbd.org/configure-special
(keyword allow_64bit_tools)

Let me know if this fixes the issue.

Re: Getting stuck at unrar stage

Posted: September 29th, 2010, 11:13 am
by grog
Yep, that seems to have done the trick. I had a hung download and a couple of other completed ones queued up behind it so I killed the sabnzbd process (shutdown failed) and changed the config file and they all completed fine after restarting. It's strange that it stopped working in the first place though. I checked my Windows Update history and there were a few security fixes applied on the day things stopped working so I suppose one of them might have been the culprit.

Anyway, thanks for the help. It seems to be working fine now which is the main thing.

Re: Getting stuck at unrar stage

Posted: September 29th, 2010, 12:38 pm
by shypike
Should it ever happen again, don't kill SABnzbd. That might corrupt your queue.
Instead stop unrar (or par2).