[
https://issues.apache.org/jira/browse/ACCUMULO-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654450#comment-14654450
]
Sean Busbey commented on ACCUMULO-3952:
---------------------------------------
stop with error message and a pointer to an ENV variable that disables the
check and I'm +1.
> 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)
