Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8160899C0 for ; Wed, 29 May 2013 18:50:20 +0000 (UTC) Received: (qmail 75753 invoked by uid 500); 29 May 2013 18:50:20 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 75720 invoked by uid 500); 29 May 2013 18:50:20 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 75711 invoked by uid 99); 29 May 2013 18:50:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 May 2013 18:50:20 +0000 Date: Wed, 29 May 2013 18:50:19 +0000 (UTC) From: "Trevor McKay (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-2219) HDFS install results in Invalid hostname exception during namenode start 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/AMBARI-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor McKay updated AMBARI-2219: --------------------------------- Attachment: hadoop-hdfs-namenode-somemachine.log > HDFS install results in Invalid hostname exception during namenode start > ------------------------------------------------------------------------ > > Key: AMBARI-2219 > URL: https://issues.apache.org/jira/browse/AMBARI-2219 > Project: Ambari > Issue Type: Bug > Components: agent, controller > Affects Versions: 1.3.0 > Environment: Fedora 16 server > RHEL 6.2 or 6.3 agent > Installing a single machine cluster with HDFS and mapreduce > Reporter: Trevor McKay > Attachments: hadoop-hdfs-namenode-somemachine.log > > > Very reproducible for me, using snapshot builds of trunk and freshly provisioned agent machines (reusing the same server after ambari-reset) > The HDFS install/start/test fails on starting the namenode with this error: > notice: /Stage[2]/Hdp-hadoop::Namenode/Hdp-hadoop::Namenode::Create_app_directories[create_app_directories]/Hdp-hadoop::Hdfs::Directory[/mapred]/Hdp-hadoop::Exec-hadoop[fs -mkdir /mapred]/Hdp::Exec[hadoop --config /etc/hadoop/conf fs -mkdir /mapred]/Exec[hadoop --config /etc/hadoop/conf fs -mkdir /mapred]/returns: 13/05/29 13:14:54 WARN fs.FileSystem: "null" is a deprecated filesystem name. Use "hdfs://null/" instead. > Is this a configuration error? Something wrong in the agent? Something erroneous sent from the server? -- 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