#470 libacl.so is not found on Debian Multiarch

[Adrian Fita]

Hello.

I was having trouble with areca getting stuck on a FIFO file, so I followed the instructions in the FAQ about enabling the support for extended attributes (I configured filesystem.accessor.impl = com.myJava.file.metadata.posix.jni.JNIMetaDataAccessor in fwk.properties), but I was keep getting the error WARNING - com.myJava.file.metadata.posix.jni.JNIMetaDataAccessor cannot be used on this system. Got the following error : "java.lang.UnsatisfiedLinkError : no acl in java.library.path".

Running areca under strace revealed that it wasn't looking for the libacl.so file in the right place. Debian Multiarch has the libacl.so file in /lib/i386-linux-gnu/libacl.so.1 (in my case. I'm not sure about where the 64bit version is at). Areca was looking anywhere, but there. For now I did a symblinkg in /lib/libacl.so and it's working, but I would really apreciate it getting it fixed properly.

I don't know whose bug is this (Areca or Java JRE), but I'm suspecting areca. If it's not its fault, let me know and I'll fill in a bug elsewhere.

Relevant info:

Debian version: Debian sid/unstable with all the latest package versions (Debian wheezy/testing -> the next stable is also multiarch, so this is relevant for that as well)

Java JRE:

java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.5) (6b24-1.11.5-1)
OpenJDK Server VM (build 20.0-b12, mixed mode)

Areca (from Help->About):

Areca Backup
Version 7.2.17 - November 17, 2012

Relevant strace:

    open("/usr/lib/jvm/java-6-openjdk-i386/jre/bin/../lib/i386/jli/libacl.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386/server/libacl.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386/libacl.so.1", O_RDONLY) = -1 ENOENT (No such file or directory)
    open("/lib/i386-linux-gnu/libacl.so.1", O_RDONLY) = 28
    stat64("/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386/libacl.so", 0xb6a4cd80) = -1 ENOENT (No such file or directory)
    stat64("/home/adrian/applications/areca/lib/libacl.so", 0xb6a4cd80) = -1 ENOENT (No such file or directory)
    stat64("/lib64/libacl.so", 0xb6a4cd80)  = -1 ENOENT (No such file or directory)
    stat64("/lib/libacl.so", 0xb6a4cd80)    = -1 ENOENT (No such file or directory)
    stat64("/usr/lib64/libacl.so", 0xb6a4cd80) = -1 ENOENT (No such file or directory)
    stat64("/usr/lib/libacl.so", 0xb6a4cd80) = -1 ENOENT (No such file or directory)
    stat64("/usr/lib64/java/libacl.so", 0xb6a4cd80) = -1 ENOENT (No such file or directory)
    stat64("/usr/lib/java/libacl.so", 0xb6a4cd80) = -1 ENOENT (No such file or directory)
    stat64("/usr/lib64/jni/libacl.so", 0xb6a4cd80) = -1 ENOENT (No such file or directory)
    stat64("/usr/lib/jni/libacl.so", 0xb6a4cd80) = -1 ENOENT (No such file or directory)
    stat64("/usr/share/java/libacl.so", 0xb6a4cd80) = -1 ENOENT (No such file or directory)

[Fernando Lozano]

Here using CentOS 6.4 same problem: Areca expects to find libacl.so but the Linux distribution names it libacl.so.1. I created a synlink for Areaca to work, but Areca could try both names before giving an error. Or the install script / start script could check and reate a synlink inside Areca install dir to the user doesn't need to know how to solve this issue.

[JN]