[
https://issues.apache.org/jira/browse/HADOOP-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538399#comment-13538399
]
Eli Reisman commented on HADOOP-7894:
-------------------------------------
Hey, did anyone ever come up with a one-size-fits-all solution to this? I am
trying to configure 2.0.2-alpha and can't get JAVA_HOME to show up. I'm running
on Ubuntu, and have gotten numerous non-YARN hadoop versions to run fine on
this machine. Even when I hardcode my JAVA_HOME into {start,stop}-dfs.sh and
{start,stop}-yarn.sh, add then to my bash profiles, source various config
scripts, etc. nothing seems to work. Will report back when something works, but
if anyone knows a quick workaround for linux right now that would be fantastic.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
