ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yusaku Sako <>
Subject Re: NameNode can't be started via Ambari Web UI --> Problematic Property is: fs.defaultFS
Date Tue, 16 Sep 2014 20:29:17 GMT
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: <localhost and other default entries>
::1 <localhost and other default entries> host1 host2 host3

Make sure that on each machine, "hostname -f" returns the FQDN (such
as 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://<FQDN of NN host>:8020" (e.g.,


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/ to server_1:8020 failed on
> connection exception: Connection refused; For
> more details see:
> In this case, the value of fs.defaultFS = hdfs://  (This ip is
> server_1's ip. I gave server_1 as the FQDN)
> 2. safemode: Call From server_1/ to localhost:9000 failed on
> connection exception: Connection refused; For
> more details see:
> 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

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.

View raw message