SABnzbd Forums

I'm running version 0.4.6, but this has been occurring since probably 0.4 or so which pretty much means it is unrar or par2 causing the problem.  Basically my computer is a headless server running 8.04 Xubuntu, 0.4 par2cmdline, 3.80 unrar.  Everything works fine most of the time, but every now and then i get a nzb from newzbin that freezes the computer during post processing, and it seems during unraring.

After restarting the computer (it won't respond at all) I can manually finish extracting the files with no problem.  I'm almost positive it did the same thing with version 3.71 unrar,  any ideas on some more things to try?

Heres the command i use to unrar  

I've tried on the same nzbs multiple times and it still freezes, so there is definitely something particular about some reports.

I'm puzzled, because I use the exact same setup for my downloading.
With one exception only: I use Ubuntu Server 8.04 (so without all the GUI stuff).
There are usually two suspects: par2cmdline and unrar.

I use the par2cmdline from the official Ubuntu repositories.

unrar 3.80, I downloaded directly from the rarlabs site: http://www.rarlab.com/rar/rarlinux-3.8.0.tar.gz
Make sure you do NOT have unrar 3.80Beta2, I have seen many complaints about that one.

I just removed the unrar and par2 packages using aptitude, yet I still have all the par2 files and rar/unrar in my usr/local/bin folder.  So it seems version 0.4 par2cmdline and version 3.80 unrar are still installed even though I removed the packages.  I know I manually installed both par2cmdline and unrar, maybe sabnzbd was using some other versions that were installed at the same time?  Whenever i typed just par2 or unrar in the commandline, I would get par2cmdline version 0.4 and unrar 3.80.

SABnzbd searches the path for these utilities.
It is possible that SABnzbd doesn't get the same path as your shell.
If you start it in init.d, the path is definitely different from an interactive shell.
Interactive shells usually extend the path.

I seemed to have fixed the problem, the nzb I have been using for testing, which freezes during unrar is now working.  What was happening is this, I had par2 and unrar both installed in /usr/local/bin, which is recognized by my commandline, but there were also an older version (3.71 Beta 2) installed in /usr/bin (installed by ubuntu repository).  I removed par2 and unrar from /usr/local/bin and installed manually version 3.80 unrar into /usr/bin.  Now it unrars that nzb just fine.