[
https://issues.apache.org/jira/browse/ACCUMULO-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930779#comment-13930779
]
ASF subversion and git services commented on ACCUMULO-2267:
-----------------------------------------------------------
Commit fc4de9022e3b82e71c4fca51e4f80b2cacb3ea90 in accumulo's branch
refs/heads/1.6.0-SNAPSHOT from [~ecn]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=fc4de90 ]
ACCUMULO-2267 added a basic config rpm, initialize hdfs for accumulo, deal with
versions on the accumulo jars, fix the start-up scripts, tested on Centos6.5
> problems running accumulo from RPM
> ----------------------------------
>
> Key: ACCUMULO-2267
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2267
> Project: Accumulo
> Issue Type: Bug
> Reporter: Michael Berman
> Assignee: Christopher Tubbs
> Fix For: 1.6.0
>
>
> - jps is called in the init.d scripts but it's not in the PATH it sets. on
> my centos box, it's in $JAVA_HOME/bin
> - in bin/accumulo, accumulo-start.jar is expected to be in
> $ACCUMULO_HOME/lib, but actually it's in $JAVA_HOME/accumulo
> - in bin/accumulo, accumulo-start.jar does not have version decoration, but
> the installed jar does
> - nothing else (other accumulo jars from $JAVA_HOME/accumulo, other
> dependencies from $ACCUMULO_HOME/lib) seems to be getting into the classpath.
> initial failure is NoClassDefFoundError:
> org/apache/commons/vfs2/provider/FileProvider
> i wonder if the standardization on RPM deployment locations is worth the
> departure from the standard accumulo deployment locations, at least for
> 1.6.0, since it seems like the impact on all the script infrastructure hasn't
> really been thought through yet, so close to the release.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
