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 5C47E11651 for ; Wed, 17 Sep 2014 08:58:19 +0000 (UTC) Received: (qmail 43984 invoked by uid 500); 17 Sep 2014 08:58:19 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 43949 invoked by uid 500); 17 Sep 2014 08:58:19 -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 43939 invoked by uid 99); 17 Sep 2014 08:58:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2014 08:58:18 +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 (athena.apache.org: domain of itharavi@gmail.com designates 209.85.216.169 as permitted sender) Received: from [209.85.216.169] (HELO mail-qc0-f169.google.com) (209.85.216.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2014 08:58:14 +0000 Received: by mail-qc0-f169.google.com with SMTP id r5so1644784qcx.0 for ; Wed, 17 Sep 2014 01:57:53 -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=2JLRwe4LH0hMFU1gESTm5nXnVPHy4b9bYea5QDP6ZEk=; b=vv6qnCMr5MewzcY/SlA+sA6pXPxbJN7skhg2iKoEP/fgAlKxu1I03VZzVBbB0nxpwy g5fMT0o4F0+wxbm+1DDMesYzV9g0n6TjOyZFQ61gzvb6r9bTn02kOzdJNdPx/lLlUqzW d7be7ZQ9/3gkVQ0r2JN3WspcPXCzMrVNAdoN+8lvjudUv3Ck8oAv1QZGgOexmixB+fNH 0G39npw/+1qhg2UNGTa7F+jOsBh2NVf6XDE69/on/T2uCwCatJSC6RaQiX4rYmsjBMwb QS0CPXpzmjWryviwxyfuJux7ivfesbC4WwoI9qgnBe1GRMT4otxJTw9GdOkK5XAfc/S5 HnVg== MIME-Version: 1.0 X-Received: by 10.236.223.36 with SMTP id u34mr18158391yhp.79.1410944273699; Wed, 17 Sep 2014 01:57:53 -0700 (PDT) Received: by 10.170.164.213 with HTTP; Wed, 17 Sep 2014 01:57:53 -0700 (PDT) In-Reply-To: References: Date: Wed, 17 Sep 2014 14:27:53 +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=001a11c202343b5b4105033f107f X-Virus-Checked: Checked by ClamAV on apache.org --001a11c202343b5b4105033f107f Content-Type: text/plain; charset=UTF-8 Yusaku, I have an update on this. In the meanwhile I did the below: - Created a brand new VM and assign the host name as server3.mycompany.com - Updated both /etc/hosts & /etc/sysconfig/network files with that hostname. - Installed both Ambari Server and Agent on the same host - Created a single node cluster via Ambari Web UI - Installed NameNode + SNameNode + DataNode + YARN + other services This time NameNode started without any issue. Without any surprise, the default value it took for fs.defaultFS was "hdfs:// server3.mycompany.com:8020" The other difference is: This time, when I gave host name as *server3.mycompany.com * , it did not say this was not a valid FQDN. However, it did give me a warning in my earlier case i.e. Server_1 So the FQDN something like Server_1 is not a good practice? Thanks for your help. ~Ravi Itha On Wed, Sep 17, 2014 at 11:40 AM, Ravi Itha wrote: > 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. >> >> > > --001a11c202343b5b4105033f107f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yusaku,
=C2=A0
I have = an update on this. In the meanwhile I did the below:
=C2=A0<= /div>
  • Created a brand new VM and assign the host name as server3.mycompany.com
  • Updat= ed both /etc/hosts & /etc/sysconfig/network files with that hostname.
  • Installed both Ambari Server and Agent on the same host
  • Crea= ted a single node cluster via Ambari Web UI
  • Installed NameNode + SN= ameNode + DataNode + YARN + other services
=C2=A0
T= his time NameNode started without any issue. Without any surprise, the defa= ult value it took for fs.defaultFS was "hdfs://server3.mycompany.com:8020"
= =C2=A0
The other difference is:
=C2=A0
=
This time, when I gave host name as server3.mycompany.com , it did not say this was not= a valid FQDN. However, it did give me a warning in my earlier case i.e. Se= rver_1
=C2=A0
So the FQDN something like Ser= ver_1 is not a good practice?
=C2=A0
Thanks = for your help.
=C2=A0
~Ravi Itha
<= div>=C2=A0
=C2=A0
=C2=A0
On Wed, Sep 17, 2014 at 11:40= AM, Ravi Itha <itharavi@gmail.com> wrote:
=C2=A0
=
Thanks Yusaku,
=C2=A0=
I am using Ambari v 1.6.1. Yes, the default value it took = for fs.defaultFS is "hdfs://server_1:8020"
=C2=A0
The output= of hostname -f is: server_1
=C2=A0
And, the contents of /etc/hosts is:
=C2=A0
127.0.0.1 localhost.localdomain localhost
::1 localhost= 6.localdomain6 localhost6
192.168.21.138=C2=A0server_1
192.168.21.137 ambar= i_server
=C2=A0
the FQDN I gave during host selecti= on was: server_1
=C2=A0
As of now, the error is:
=C2=A0
safemode: Incomplete HDFS URI, no host: hdfs://serv= er_1:8020
2014-09-16 23:02:41,225 - Retrying after 10 seconds. Reason: = Execution of 'su - hdfs -c 'hadoop dfsadmin -safemode get' | gr= ep 'Safe mode is OFF'' returned 1. DEPRECATED: Use of this scri= pt to execute hdfs command is deprecated.
Instead use the hdfs co= mmand for it.
=C2=A0
safemode: Incomplete HDFS URI, no = host: hdfs://server_1:8020
=C2=A0
=C2=A0
Please advise where I am making the mistake?
<= span>
=C2=A0
-Ravi
= =C2=A0
On Wed, Sep 17, 2014 at 1:59 AM, Yus= aku Sako <yusaku@hortonworks.com> wrote:
=C2=A0
Hi Ravi,
=C2=A0
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:
=C2=A0
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
=C2=A0
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.=
=C2=A0
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.,
=C2=A0
Yusaku
=C2=A0
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
>
> 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
>
> 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
>
>
>
=C2=A0
=C2=A0
--
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
<= div> received this communication in error, please contact the sender immediately=
and delete it from your system. Thank You.
=C2=A0
=C2=A0
=C2=A0
--001a11c202343b5b4105033f107f--