Unrar problem [Synology]

[thefog]

Since I have updated to the lasted version (0.7.16-7) on my Synology DS 213+ (DSM 4.3) unrar is not working anymore
With the older Sabnzbd version everything was fine.

I found following entry in the log-file:
2013-10-03 16:43:20,445::INFO::[newsunpack:714] Skipping unrar file check due to unreliable file names or old unrar
2013-10-03 16:43:20,446::INFO::[newsunpack:719] 0 Datei(en)/Ordner entpackt in 0 Sekunden

filename: upz4jagbxy9st282woznoa

any ideas how to fix this issue?

[shypike]

The older SABnzbd and exactly the same NZB?
Looks like one with very obscure file names.

[thefog]

yes, with the old version and the same filename everything was fine.

[shypike]

Which version of SABnzbd was that?
Did you also upgrade unrar?
We have no control over the unrar version.

[manuxi]

Same here, can't get it to work since the update.
Tried uninstalling und reinstalling with no luck.
Did you figure it out what the problem might be?

[thefog]

to be honest I don`t know which version was installed before I have updated. If I remember correctly I have installed the old version for about 4 months.

Nope, I don´t have upgraded unrar - I installed the synocommunity sabnzbd package. I don´t have a clue how to update unrar?
Of course I have also re-installed sabnzbd without success

[shypike]

You'll have to talk to the "community" that created the package.

[dougunder]

I'm having the exact same same problem using optware-android.
I tried compiling unrar v5 last night, but get complaints about libstdc++.so.6 when running I'd probably need to upgrade gcc too, which would likely break all kinds of things.

All things considered just going to downgrade till optware gets updated. Can you guys tell me what the latest version working with unrar v4 was?

I installed using the python sources, if that makes a difference. Latest in optware unstable repo is 0.5.6.1

[shypike]

. Can you guys tell me what the latest version working with unrar v4 was?

We support anything after 3.50.
The trouble is we have no idea if just any individual ported version is ok,

[cytec]

i've opened a ticket for this: https://github.com/SynoCommunity/spksrc/issues/693

seems like unrar 5 is not working correctly. Since unrar 3.8 is installed by default in /usr/syno/bin you can just rename/delete the unrar binary in /usr/local/sabnzbd/bin/ and restart SAB, it should then use the binary in /usr/syno/bin

[manuxi]

Great, it's working again. Thank you!
I copied the unrar from usr/syno/bin to usr/local/sabnzbd/bin...

[sander]

FYI & FWIW:

On my Linux (Ubuntu 13.04, 64-bit), I use unrar 5, and everything works in SABnzbd. So my statement is that it is not a problem with unrar5 itself. So it must something specific for Synology.

HTH

Code: Select all

sander@flappie:~$ unrar

UNRAR 5.00 freeware      Copyright (c) 1993-2013 Alexander Roshal

Usage:     unrar <command> -<switch 1> -<switch N> <archive> <files...>
               <@listfiles...> <path_to_extract\>

<Commands>
  e             Extract files without archived paths
  l[t[a],b]     List archive contents [technical[all], bare]
  p             Print file to stdout
  t             Test archive files
  v[t[a],b]     Verbosely list archive contents [technical[all],bare]
  x             Extract files with full path

<Switches>
  -             Stop switches scanning
  @[+]          Disable [enable] file lists
  ad            Append archive name to destination path
  ag[format]    Generate archive name using the current date
  ai            Ignore file attributes
  ap<path>      Set path inside archive
  c-            Disable comments show
  cfg-          Disable read configuration
  cl            Convert names to lower case
  cu            Convert names to upper case
  dh            Open shared files
  ep            Exclude paths from names
  ep3           Expand paths to full including the drive letter
  f             Freshen files
  id[c,d,p,q]   Disable messages
  ierr          Send all messages to stderr
  inul          Disable all messages
  kb            Keep broken extracted files
  n<file>       Additionally filter included files
  n@            Read additional filter masks from stdin
  n@<list>      Read additional filter masks from list file
  o[+|-]        Set the overwrite mode
  or            Rename files automatically
  ow            Save or restore file owner and group
  p[password]   Set password
  p-            Do not query password
  r             Recurse subdirectories
  sl<size>      Process files with size less than specified
  sm<size>      Process files with size more than specified
  ta<date>      Process files modified after <date> in YYYYMMDDHHMMSS format
  tb<date>      Process files modified before <date> in YYYYMMDDHHMMSS format
  tn<time>      Process files newer than <time>
  to<time>      Process files older than <time>
  ts<m,c,a>[N]  Save or restore file time (modification, creation, access)
  u             Update files
  v             List all volumes
  ver[n]        File version control
  vp            Pause before each volume
  x<file>       Exclude specified file
  x@            Read file names to exclude from stdin
  x@<list>      Exclude files listed in specified list file
  y             Assume Yes on all queries
sander@flappie:~$

[cytec]

thats not 100% percent correcty.
for me unrar 5 works like 50% of the time. but somehow it seems lile it can't hanle metadata password nzb files and some other stuff that 3.8. could without any problems.

i think its more a SAB/unrar 5 compatibility bug than a synology specific thing. (the whole thing can be read in the issue i mentioned above)

[sander]

Do you mean unrar5 works for you if there are no rar-passwords, and there are / might be problems in the case of rar-passwords?

[cytec]

yes, but the patch you provided here: http://forums.sabnzbd.org/viewtopic.php?f=3&t=16166 fixes this
so we just have to wait for this to become included in the next release, for the meantime i've opened a pull request with that patch over at SynoCommunity.

Thanks again