[
https://issues.apache.org/jira/browse/HDFS-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108226#comment-13108226
]
Aaron T. Myers commented on HDFS-2303:
--------------------------------------
I bumped into this issue earlier today while getting a secure cluster working
on Ubuntu.
Looks like the {{jsvc}} binary that's downloaded as part of the trunk build was
compiled against libcap1, while Ubuntu Maverick and later ships libcap2. As a
result, if you try to run {{jsvc}} from an Ubuntu box, you'll get something
like this error:
{noformat}
hadoop-hdfs-project/hadoop-hdfs/target/hadoop-hdfs-0.24.0-SNAPSHOT/libexec/jsvc:
error while loading shared libraries: libcap.so.1: cannot open shared object
file: No such file or directory
{noformat}
Since I like to live on the edge, I tried just sym-linking {{/lib/libcap.so.1
-> /lib/libcap.so.2}}, and this appears to have worked for {{jsvc}} - I can now
run a secure DN. But, we should obviously get this resolved in a reasonable way.
> jsvc needs to be recompilable
> -----------------------------
>
> Key: HDFS-2303
> URL: https://issues.apache.org/jira/browse/HDFS-2303
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
>
> It would be nice to recompile jsvc as part of the native profile. This has a
> number of benefits including an ability to re-generate all binary artifacts,
> etc. Most of all, however, it will provide a way to generate jsvc on Linux
> distributions that don't have matching libc
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
