Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DB889EAD1 for ; Fri, 11 Jan 2013 06:00:26 +0000 (UTC) Received: (qmail 91188 invoked by uid 500); 11 Jan 2013 06:00:23 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 89709 invoked by uid 500); 11 Jan 2013 06:00:22 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 89613 invoked by uid 99); 11 Jan 2013 06:00:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2013 06:00:20 +0000 Date: Fri, 11 Jan 2013 06:00:20 +0000 (UTC) From: "Eli Reisman (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-7894) bin and sbin commands don't use JAVA_HOME when run from the tarball MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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