Return-Path: X-Original-To: apmail-ambari-user-archive@www.apache.org Delivered-To: apmail-ambari-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 226D511246 for ; Wed, 17 Sep 2014 06:10:59 +0000 (UTC) Received: (qmail 2381 invoked by uid 500); 17 Sep 2014 06:10:58 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 2345 invoked by uid 500); 17 Sep 2014 06:10:58 -0000 Mailing-List: contact user-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ambari.apache.org Delivered-To: mailing list user@ambari.apache.org Received: (qmail 2334 invoked by uid 99); 17 Sep 2014 06:10:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2014 06:10:58 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of itharavi@gmail.com designates 209.85.216.41 as permitted sender) Received: from [209.85.216.41] (HELO mail-qa0-f41.google.com) (209.85.216.41) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2014 06:10:32 +0000 Received: by mail-qa0-f41.google.com with SMTP id f12so1259105qad.14 for ; Tue, 16 Sep 2014 23:10:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=gEAkY2iR0Wbc3pb7SB+NHFsz2DlHljsOS9q36cWDgYY=; b=BhNzT+rqs6lLtygydz7pCirtbfLX50CksES7B+NvnXKD0wVLpODxrA3cNShr/RKAIh yayIlirJR5ApG4DDdHrzkcoBdyCjR7Vjr5PvtnqAehGIbz1OvzK5zZfQJLXA97V7n4zc q03eBZp3ZlKKsnL6OnZKvSxrv6r9EV4Ympv1NxB+DXte/ku7CeU8CgsHLo1VPboK4xL6 0+rqwzVEdj8dIskfMSglbq1h3FhMcYNgswQzwXJShA69nhyYE1LREzj4IhRzz75+xXPh wE10sFuE+jAYng3VgdLVTbUzmCoT7aeiPvKc2ZZsi6+wc+H0JRr4xYu1c8kksOux49CU uYwQ== MIME-Version: 1.0 X-Received: by 10.236.109.130 with SMTP id s2mr5096164yhg.51.1410934231464; Tue, 16 Sep 2014 23:10:31 -0700 (PDT) Received: by 10.170.164.213 with HTTP; Tue, 16 Sep 2014 23:10:31 -0700 (PDT) In-Reply-To: References: Date: Wed, 17 Sep 2014 11:40:31 +0530 Message-ID: Subject: Re: NameNode can't be started via Ambari Web UI --> Problematic Property is: fs.defaultFS From: Ravi Itha To: user@ambari.apache.org Content-Type: multipart/alternative; boundary=047d7b5d585cab028a05033cb95e X-Virus-Checked: Checked by ClamAV on apache.org --047d7b5d585cab028a05033cb95e Content-Type: text/plain; charset=UTF-8 Thanks Yusaku, I am using Ambari v 1.6.1. Yes, the default value it took for fs.defaultFS is "hdfs://server_1:8020" The output of hostname -f is: server_1 And, the contents of /etc/hosts is: 127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 192.168.21.138 server_1 192.168.21.137 ambari_server the FQDN I gave during host selection was: server_1 As of now, the error is: safemode: Incomplete HDFS URI, no host: hdfs://server_1:8020 2014-09-16 23:02:41,225 - Retrying after 10 seconds. Reason: Execution of 'su - hdfs -c 'hadoop dfsadmin -safemode get' | grep 'Safe mode is OFF'' returned 1. DEPRECATED: Use of this script to execute hdfs command is deprecated. Instead use the hdfs command for it. safemode: Incomplete HDFS URI, no host: hdfs://server_1:8020 Please advise where I am making the mistake? -Ravi On Wed, Sep 17, 2014 at 1:59 AM, Yusaku Sako wrote: > Hi Ravi, > > What version of Ambari did you use, and how did you install the cluster? > Not sure if this would help, but on small test clusters, you should > define /etc/hosts on each machine, like so: > > 127.0.0.1 > ::1 > 192.168.64.101 host1.mycompany.com host1 > 192.168.64.102 host2.mycompany.com host2 > 192.168.64.103 host3.mycompany.com host3 > > Make sure that on each machine, "hostname -f" returns the FQDN (such > as host1.mycompany.com) and "hostname" returns the short name (such as > host1). Also, make sure that you can resolve all other hosts by FQDN. > > fs.defaultFS is set up automatically by Ambari and you should not have > to adjust it, provided that the networking is configured properly. > Ambari sets it to "hdfs://:8020" (e.g., > "hdfs://host1.mycompany.com:8020) > > Yusaku > > On Tue, Sep 16, 2014 at 12:00 PM, Ravi Itha wrote: > > All, > > > > My Ambari cluster setup is below: > > > > Server 1: Ambari Server was installed > > Server 2: Ambari Agent was installed > > Server 3: Ambari Agent was installed > > > > I create cluster with Server 2 and Server 3 and installed > > > > Server 2 has NameNode > > Server 3 has SNameNode & DataNode > > > > When I try to start NameNode from UI, it does not start > > > > Following are the errors: > > > > 1. safemode: Call From server_1/192.168.21.138 to server_1:8020 failed > on > > connection exception: java.net.ConnectException: Connection refused; For > > more details see: http://wiki.apache.org/hadoop/ConnectionRefused > > > > In this case, the value of fs.defaultFS = hdfs://192.168.21.138 (This > ip is > > server_1's ip. I gave server_1 as the FQDN) > > > > 2. safemode: Call From server_1/192.168.21.138 to localhost:9000 failed > on > > connection exception: java.net.ConnectException: Connection refused; For > > more details see: http://wiki.apache.org/hadoop/ConnectionRefused > > > > In this case, the value of fs.defaultFS = hdfs://localhost > > > > Also, I cannot leave this field as blank. > > > > So can someone, please help me what should be the right value to be set > here > > and I how I can fix the issue. > > > > ~Ravi Itha > > > > > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. > --047d7b5d585cab028a05033cb95e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks Yusaku,

I am using Am= bari v 1.6.1. Yes, the default value it took for fs.defaultFS is "hdfs://server_1:8020"

The output of hostname = -f is: server_1

And, the= contents of /etc/hosts is:

127.0.0.1 localhost.loc= aldomain localhost
::1 localhost6.localdomain6 localhost6
192.168.21.= 138=C2=A0server_1
192.168.21.137 ambari_server
<= span>
the FQDN I gave during host selection was: server_1

As of now,= the error is:

safemode: Incomplete HDFS URI, no h= ost: hdfs://server_1:8020
2014-09-16 23:02:41,225 - Retrying after 10 se= conds. Reason: Execution of 'su - hdfs -c 'hadoop dfsadmin -safemod= e get' | grep 'Safe mode is OFF'' returned 1. DEPRECATED: U= se of this script to execute hdfs command is deprecated.
Instead use the= hdfs command for it.

safemode: Incomplete HDFS URI, no host: hdfs:/= /server_1:8020


Please advise where = I am making the mistake?

-Ravi

On Wed, Sep 17, 2014 at 1= :59 AM, Yusaku Sako <yusaku@hortonworks.com> wrote:
=
Hi Ravi,

What version of Ambari did you use, and how did you install the cluster? Not sure if this would help, but on small test clusters, you should
define /etc/hosts on each machine, like so:

127.0.0.1 <localhost and other default entries>
::1 <localhost and other default entries>
192.168.64.101 hos= t1.mycompany.com host1
192.168.64.102 hos= t2.mycompany.com host2
192.168.64.103 hos= t3.mycompany.com host3

Make sure that on each machine, "hostname -f" returns the FQDN (s= uch
as host1.mycompany= .com) and "hostname" returns the short name (such as
host1).=C2=A0 Also, make sure that you can resolve all other hosts by FQDN.=

fs.defaultFS is set up automatically by Ambari and you should not have
to adjust it, provided that the networking is configured properly.
Ambari sets it to "hdfs://<FQDN of NN host>:8020" (e.g., "hdfs://= host1.mycompany.com:8020)

Yusaku

On Tue, Sep 16, 2014 at 12:00 PM, Ravi Itha <itharavi@gmail.com> wrote:
> All,
>
> My Ambari cluster setup is below:
>
> Server 1: Ambari Server was installed
> Server 2: Ambari Agent was installed
> Server 3: Ambari Agent was installed
>
> I create cluster with Server 2 and Server 3 and installed
>
> Server 2 has NameNode
> Server 3 has SNameNode & DataNode
>
> When I try to start NameNode from UI, it does not start
>
> Following are the errors:
>
> 1. safemode: Call From server_1/192.168.21.138 to server_1:8020 failed on
> connection exception: java.net.ConnectException: Connection refused; F= or
> more details see:=C2=A0 http://wiki.apache.org/hadoop/ConnectionRef= used
>
> In this case, the value of fs.defaultFS =3D hdfs://192.168.21.138=C2=A0 (This ip is
> server_1's ip. I gave server_1 as the FQDN)
>
> 2. safemode: Call From server_1/192.168.21.138 to localhost:9000 failed on
> connection exception: java.net.ConnectException: Connection refused; F= or
> more details see:=C2=A0 http://wiki.apache.org/hadoop/ConnectionRef= used
>
> In this case, the value of fs.defaultFS =3D hdfs://localhost
>
> Also, I cannot leave this field as blank.
>
> So can someone, please help me what should be the right value to be se= t here
> and I how I can fix the issue.
>
> ~Ravi Itha
>
>
>

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to=
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that=
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately=
and delete it from your system. Thank You.

--047d7b5d585cab028a05033cb95e--