Support Forum

ln -s /usr/local/bin/rar /usr/bin fixed it, but its strange that it wouldn't find it even tho my path was correct.

little more info...

[beezel@julian ~]$ which rar
/usr/local/bin/rar
[beezel@julian ~]$ $PATH
-bash: /usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:

and im starting sab as user beezel

shy, thanks for the quick reply. i removed unrar via yum and installed the x64 from rarlabs.com, but now sab isn't seeing rar at all. i checked sabnzbd.ini but couldn't find a place to specify where rar is located. im seeing: unrar binary... NOT found tho a simple rar or unrar yeilds:  unrar UNRAR 3...

I'm on fc10, and unfortunately it looks like ive been abandoned a while back version-wise: Installed Packages unrar.x86_64                  3.7.8-3.fc10                    installed Available Packages unrar.x86_64                  3.7.8-3.fc10                    rpmfusion-nonfree is there any reason...

ok, so rpm -e --nodeps killed yum, so i had to wget expat-2.0.1-5 from a repo and install it via rpm -ihv instead. easy fix, after blacklisting expat from yum.

im thinking:

rpm -e -nodeps expat-2.0.1-8.fc10.x86_64
rpm -e -nodeps expat-devel-2.0.1-8.fc10.x86_64

yum --allow-downgrade install expat*-5.fc10.x86_64

does this sound appropriate? just trying not to hose my box and end up working all weekend

  Today I upgraded from expat-2.0.1-7 to expat-2.0.1-8 and found sabnzbd+ 0.5.0beta1 stopped taking nzbs with the error message below. To fix it I downgraded back to expat-2.0.1-7. Then sabnzbd+ started working again.   expat-2.0.1-8 seems to be a security release. Below is the changelog. Error mes...