No UNRAR program found

Support for the Debian/Ubuntu package, created by JCFP.
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
anothernickname
Newbie
Newbie
Posts: 1
Joined: November 8th, 2011, 5:24 pm

No UNRAR program found

Post by anothernickname »

Apologies if this is covered elsewhere, I've read over the FAQ, googled, and searched the support forum without finding any results.

Yesterday I installed sabnzbd 0.5.4 from the debian squeeze repository, and have it running as a daemon using the /etc/init.d/sabnzbdplus script that's provided in the package. Everything seems to work fine, except for a big fat red "No UNRAR program found, unpacking RAR files is not possible" message on the UI's main page, and repeated errors in the log to the effect of:

Code: Select all

ERROR:
Error "[Errno 2] No such file or directory" while running rar_unpack on blah
I do have unrar installed (from the debian squeeze nonfree repo) in /usr/bin/runrar. Permissions seem right, I can run it as a normal user, and I can unrar archives I create with winrar on another machine.

I'm assuming unrar just needs to be somewhere else so sabnzbd can locate it? Can someone clue me where that might be, so I can simlink to it?

Thanks!
User avatar
jcfp
Release Testers
Release Testers
Posts: 1032
Joined: February 7th, 2008, 12:45 pm

Re: No UNRAR program found

Post by jcfp »

The program's log file can tell, it looks for and log all helper programs it finds on startup. Might be some path issue, although init scripts would normally automatically be supplied with a proper path including at least /usr/bin and /bin. Also, the output of 'ls -la `which unrar`' and the output of 'unrar | head -n5' could be helpful.
Post Reply