SABnzbd Forums

Hey!

I downloaded and started to use the beta of SABnzbd+ 0.5.0Beta1 a few days ago, it worked flawlessly, but now it seems to be stuck on a repair, its still 29% after atleast 16-17 hours.
http://img248.imageshack.us/img248/9058/sabsuck.png - pic
What shall I do?

And another strange thing is that the "Completed"-time on all the queued downloads, plus the download its repairing seems to be changing time everytime i refresh my browser-window.

Restart SABnzbd and it should try that file again, then go through the remaining queue.

Didn't work, I've restared SAB, and the computer, and nothing helps.. So I had to purge my history and unpack automaticly and it started to work on new downloads..

b0bber wrote: Didn't work, I've restared SAB, and the computer, and nothing helps.. So I had to purge my history and unpack automaticly and it started to work on new downloads..

In what didn't it work.
Did the stuck item just sit there in the history?
Could you see that SABnzbd actually tried to run the verification again?

One possibility is that the repair process crashes and that each restart
just makes it try and crash again.
We would need log files or at least the NZB file that is causing the problem.

This has happend to me as well at least 4 times. The repair hang indeffentantely while par2.exe is running at a very high cpu load in taskmanager (90-100%) this will go on untill sab and par2.exe is killed from the task manager.
After you have killed the processes and restarted sab it will continue post processing the queue.

btw im running 0.5 (beta4)
Windows 7 64 bit
used the exe for installation (i think)
windows (MS) firewall and anti virus

Can you email an example of an NZB that shows this behaviour to bugs at sabnzbd.org ?
I'm getting second thoughts about promoting par2-tbb as primary par2 program.
Maybe we should go back to the classic 32bit single-core version.

As a test you can remove par2.exe and replace it with par2-classic.exe.
(check the x64 folder too).

It dosen't seem to be linked to a specific nzb file, as downloading the nzb file again normally resulst in sab repearing without any issues. It has happend on files ranging from 2.5gb to 17gb, so size doesn't seem to mather either.

I will however try and switch to the old par process and download a bunch of files to see if i can make it fail over again.

Merry x-mas. and thanks for an awsome program.

I have encountered this too... with Beta6.
SABnzbdb sites on repair forever... restart of sabnzbdb and windows does not resolve.
Even deleting of the history item was a task... took ab out 50 tries and it finally took.
This has occurred on several different .nzb files (large and small).

I download a fare bit... constant 300 KB/s.
This has occurred on about 5 different occasions so far.

Cheers,
TechDude

We have little or no control over the behaviour of the par2 utility.
par2 does require correctly working memory.

One thing you can try is to replace the par2.exe files
with par2-classic.exe.
If even that still hangs up, your memory may be a fringe case.

I reinstalled Windows 7 today (x64). Installed beta 6.

A few nzb's worked but now it stops at Repair: Quick Checking.

UnRAR.exe is running but isn't doing anything, using 112K of memory, 0% CPU usage.

The logfile is saying "Extracting rarfile D:\sabnzb\incomplete...." but nothing happens.

Any suggestions on what I could try?

Start the task manager and kill the unrar process.
Stop and restart SABnzbd.
If it keeps getting stuck, there might something wrong with the rar files.
If so, you could try WinRar (you can evaluate before buying) to get more info.

Tried it and it's the same result, however now it stopped at "extracting".

UnRAR.exe is running at 0% usage (and 112K RAM).

It creates the _UNPACK_****-folder, but doesn't start to unpack.
I can unpack it manually perfectly fine with WinRAR.

I completely removed it and installed 0.4.12 again and it's working perfectly fine..

Odd, SABnzbd-0.4.12 contains an older version of unrar
and only the 32bit version of it.

I had this issue also, but I had changed the par2 flags to -t+ hoping for better results. After I had the issue i set it back to -t0 and haven't had it since.