[
https://issues.apache.org/jira/browse/HADOOP-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550864#comment-13550864
]
Eli Reisman commented on HADOOP-7894:
-------------------------------------
You know, I did, and it didn't pick up. I also tried the env_keep sudoers fix
mentioned in another thread, etc. and no dice. In the end (running ubuntu) I
had to hardcode the JAVA_HOME and a few other env vars into the env scripts in
the run scripts in order to get my 2.0.2-alpha YARN, HDFS, and MR all running
successfully. I'm on the wrong machine but if you're curious let me know and I
can post a more detailed idea of what ended up working, if it helps diagnose
the problem. Its certainly not ideal, but it is getting me by for now. Thanks
for the advice!
> 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
