Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 10 Mar 2014 17:16:45 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12691675.1390930774979.36491.1394471805772@arcas>
In-Reply-To: <JIRA.12691675.1390930774979@arcas>
References: <JIRA.12691675.1390930774979@arcas>
Subject: [jira] [Commented] (ACCUMULO-2267) problems running accumulo from
 RPM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925910#comment-13925910 ] 

Christopher Tubbs commented on ACCUMULO-2267:
---------------------------------------------

I don't think status_of_proc is part of LSB 4.0, which is on CentOS. It's part of 3.2 <= LSB < 4.0
It might be better to have RPM init scripts that use /etc/init.d/functions, provided by the initscripts package, for CentOS.

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