You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2014/03/11 19:59:50 UTC

[jira] [Resolved] (ACCUMULO-2267) problems running accumulo from RPM

     [ https://issues.apache.org/jira/browse/ACCUMULO-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Newton resolved ACCUMULO-2267.
-----------------------------------

    Resolution: Fixed

Please to test out and open new tixets for any remaining issues.

Tested against the CDH4 rpms on Centos 6.5.

I'm the worlds worst rpm writer... I did the minimal things to get Christopher's initial work to run on a single-node instance.


> 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)