You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/02/08 19:12:35 UTC
[jira] [Resolved] (HADOOP-7894) bin and sbin commands don't use
JAVA_HOME when run from the tarball
[ https://issues.apache.org/jira/browse/HADOOP-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved HADOOP-7894.
--------------------------------------
Resolution: Not a Problem
Fixed in trunk.
> bin and sbin commands don't use JAVA_HOME when run from the tarball
> ---------------------------------------------------------------------
>
> Key: HADOOP-7894
> URL: https://issues.apache.org/jira/browse/HADOOP-7894
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 0.23.0
> Reporter: Eli Collins
>
> When running eg ./sbin/start-dfs.sh from a tarball the scripts complain JAVA_HOME is not set and could not be found even if the env var is set.
> {noformat}
> hadoop-0.24.0-SNAPSHOT $ echo $JAVA_HOME
> /home/eli/toolchain/jdk1.6.0_24-x64
> hadoop-0.24.0-SNAPSHOT $ ./sbin/start-dfs.sh
> log4j:ERROR Could not find value for key log4j.appender.NullAppender
> log4j:ERROR Could not instantiate appender named "NullAppender".
> Starting namenodes on [localhost]
> localhost: Error: JAVA_HOME is not set and could not be found.
> {noformat}
> I have to explicitly set this via hadoop-env.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)