Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 4 Aug 2015 02:32:05 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12850656.1438365273000.362883.1438655524999@Atlassian.JIRA>
In-Reply-To: <JIRA.12850656.1438365273000@Atlassian.JIRA>
References: <JIRA.12850656.1438365273000@Atlassian.JIRA>
 <JIRA.12850656.1438365273036@arcas>
Subject: [jira] [Commented] (ACCUMULO-3952) bin/accumulo should verify
 log4j.jar was found
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Elser commented on ACCUMULO-3952:
--------------------------------------

bq. I don't think it's wise to check for log4j in the environment. We've been slowly making our way toward pure slf4j-api consumption

I don't understand the hesitation. The same goes for the slf4j jars. If they can't be found, we can't reasonably expect to run Accumulo at all.

bq. What do you envision this verification doing, Josh?

{{bin/accumulo}}

> bin/accumulo should verify log4j.jar was found
> ----------------------------------------------
>
>                 Key: ACCUMULO-3952
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3952
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: scripts
>    Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.6.3, 1.7.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.4, 1.7.1, 1.8.0
>
>
> Just spent a few hours trying to wrangle this one down. Ambari was failing to start all Accumulo components. After digging in, I realized that when Ambari was invoking {{accumulo}}, it was failing to find the log4j jar.
> It turns out this was a deployment issue where the home directory for the {{accumulo}} user was never created and the find command failed:
> {noformat}
> find: cannot stat current directory: Permission denied
> {noformat}
> Sadly, I couldn't find this error until I manually edited the accumulo script to remove the {{2>/dev/null}} redirect. We should have been able to realize that we never found the log4j jar and then clearly printed an error and exited instead of leading me on a goosechase by silently proceeding.
> Same goes for the slf4j jars.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)