Hi Everyone,
I've been running SABnzbd for 2 years now, and I'll be honest, I've only updated a couple of times in that time (If it ain't broke and all that). Anyway, a few days ago I decided to start using Sickbeard, and I had issues getting up and running with it, so I update SABnzbd to the latest version.
All was well in the world after this, and Sickbeard was up and running quite happily. And I thought "While I'm at it, I'll get rid of the "Your UNRAR version is not recommended, get it from http://www.rarlab.com/rar_add.htm" message (how stupid was I?!).
So, I update to Unrar 4.0.1, and suddenly SABnzbd doesn't unrar anything. So I procede to try every RPM version of unrar I can get my hands on, and not one of them will work (from 3.71 to 4.0.7). I try the rarlab.com link, and that doesn't work at all no matter what I try.
Any ideas?
Here's some system info:
Centos 5.7 (latest update, done to try and fix the issues)
"UNRAR 4.00 freeware Copyright (c) 1993-2011 Alexander Roshal" (4.0.7-1.el5.rf from rpm)
SABnzbd 0.6.9
Intel(R) XEON(TM) CPU 2.40GHz
6gig RAM
Swap @ 4 Gig (I've heard about memory issues)
I'm seeing this error in debug logging:
"2011-09-18 23:22:00,474::INFO::[newsunpack:644] Skipping unrar file check due to unreliable file names or old unrar"
Seriously, any help would be greatly appreciated! Like maybe the best version of unrar to run?
Unrar issue
Forum rules
Help us help you:
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.
-
evilweasil
- Newbie

- Posts: 4
- Joined: September 18th, 2011, 5:13 pm
Re: Unrar issue
I forgot to mention a couple of things:
unrar can be called without issue from the command line, and it's definately in $PATH
unrar can be called without issue from the command line, and it's definately in $PATH
Re: Unrar issue
Hi,
Can you post the output of "unrar | head"
Here's mine (that is found OK by SAB):
Reason: below is the check of SABnzbd on a correct unrar version: SAB wants to see "RAR", then a certain format, and then "Alexander Roshal". Maybe the output of your unrar looks a bit different.
Can you post the output of "unrar | head"
Here's mine (that is found OK by SAB):
Code: Select all
sander@R540:~$ unrar | head
UNRAR 4.00 beta 3 freeware Copyright (c) 1993-2010 Alexander Roshal
Usage: unrar <command> -<switch 1> -<switch N> <archive> <files...>
<@listfiles...> <path_to_extract\>
<Commands>
e Extract files to current directory
l[t,b] List archive [technical, bare]
p Print file to stdout
sander@R540:~$
Reason: below is the check of SABnzbd on a correct unrar version: SAB wants to see "RAR", then a certain format, and then "Alexander Roshal". Maybe the output of your unrar looks a bit different.
Code: Select all
def unrar_check(rar):
""" Return True if correct version of unrar is found """
if rar:
try:
version = subprocess.Popen(rar, stdout=subprocess.PIPE, stderr=subprocess.PIPE, shell=True).stdout.read()
except:
return False
m = re.search("RAR\s(\d+)\.(\d+)\s+.*Alexander Roshal", version)
if m:
return (int(m.group(1)), int(m.group(2))) >= (3, 80)
return False-
evilweasil
- Newbie

- Posts: 4
- Joined: September 18th, 2011, 5:13 pm
Re: Unrar issue
Hi there,
I posted the following in my original post:
"UNRAR 4.00 freeware Copyright (c) 1993-2011 Alexander Roshal"
Do you need anything more?
Thanks :-)
I posted the following in my original post:
"UNRAR 4.00 freeware Copyright (c) 1993-2011 Alexander Roshal"
Do you need anything more?
Thanks :-)
-
evilweasil
- Newbie

- Posts: 4
- Joined: September 18th, 2011, 5:13 pm
Re: Unrar issue
All fixed....
It turned out I had /usr/local/bin/rar which it defaulted to rather than /usr/bin/unrar (strange when /local/ comes afterwards in $PATH. Removed it, and all good :-)
It turned out I had /usr/local/bin/rar which it defaulted to rather than /usr/bin/unrar (strange when /local/ comes afterwards in $PATH. Removed it, and all good :-)
Re: Unrar issue
For the record: can you post the ' .../unrar | head ' of both unrar's here in this thread?evilweasil wrote:All fixed....
It turned out I had /usr/local/bin/rar which it defaulted to rather than /usr/bin/unrar (strange when /local/ comes afterwards in $PATH. Removed it, and all good :-)