Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

ambari + Standby NameNode not started

Solved Go to solution
Highlighted

ambari + Standby NameNode not started

please advice what is the solution for this problem

we are getting this errors ( from the log under /var/lib/ambari-agent/data )

2017-11-13 11:49:49,056 - Getting jmx metrics from NN failed. URL: http://master01.sys56.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
Traceback (most recent call last):ExecutionFailed: Execution of 'curl -s 'http://master01.sys56.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'

we also tried this solution but without results: https://community.hortonworks.com/articles/114869/how-to-resolve-namenode-nn1-is-not-listed-as-activ...

and when we try it manual

curl -s 'http://master01.sys56:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'

we get

 echo $?

7
Michael-Bronson
1 ACCEPTED SOLUTION

Accepted Solutions

Re: ambari + Standby NameNode not started

we solved this issue by do the following:

we notice that no SSH from the host with ( ambari-server ) to all machines in the cluster ,

so we copy the public key from the master machine ( ambari-server ) to each machine in the cluster , and restart the node that ( Standby NameNode ) was downe

Michael-Bronson
1 REPLY 1

Re: ambari + Standby NameNode not started

we solved this issue by do the following:

we notice that no SSH from the host with ( ambari-server ) to all machines in the cluster ,

so we copy the public key from the master machine ( ambari-server ) to each machine in the cluster , and restart the node that ( Standby NameNode ) was downe

Michael-Bronson