<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: ambari + Standby  NameNode  not started in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-Standby-NameNode-not-started/m-p/201521#M71659</link>
    <description>&lt;P&gt;we solved this issue by do the following:&lt;/P&gt;&lt;P&gt;we notice that no SSH from the host with ( ambari-server ) to all machines in the cluster , &lt;/P&gt;&lt;P&gt;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   &lt;/P&gt;</description>
    <pubDate>Thu, 23 Nov 2017 21:44:32 GMT</pubDate>
    <dc:creator>mike_bronson7</dc:creator>
    <dc:date>2017-11-23T21:44:32Z</dc:date>
    <item>
      <title>ambari + Standby  NameNode  not started</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-Standby-NameNode-not-started/m-p/201520#M71658</link>
      <description>&lt;P&gt;please advice what is the solution for this problem&lt;/P&gt;&lt;P&gt;we are getting this errors ( from the log under /var/lib/ambari-agent/data ) &lt;/P&gt;&lt;PRE&gt;2017-11-13 11:49:49,056 - Getting jmx metrics from NN failed. URL: &lt;A href="http://master01.sys56.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem" target="_blank"&gt;http://master01.sys56.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem&lt;/A&gt;
Traceback (most recent call last):ExecutionFailed: Execution of 'curl -s 'http://master01.sys56.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'&lt;/PRE&gt;&lt;P&gt;we also tried this solution but without results: &lt;A href="https://community.hortonworks.com/articles/114869/how-to-resolve-namenode-nn1-is-not-listed-as-activ.html" target="_blank"&gt;https://community.hortonworks.com/articles/114869/how-to-resolve-namenode-nn1-is-not-listed-as-activ.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;and when we try it manual&lt;/P&gt;&lt;PRE&gt;curl -s 'http://master01.sys56:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'&lt;/PRE&gt;&lt;P&gt;we get&lt;/P&gt;&lt;PRE&gt; echo $?

7&lt;/PRE&gt;</description>
      <pubDate>Thu, 23 Nov 2017 19:59:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-Standby-NameNode-not-started/m-p/201520#M71658</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-11-23T19:59:37Z</dc:date>
    </item>
    <item>
      <title>Re: ambari + Standby  NameNode  not started</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-Standby-NameNode-not-started/m-p/201521#M71659</link>
      <description>&lt;P&gt;we solved this issue by do the following:&lt;/P&gt;&lt;P&gt;we notice that no SSH from the host with ( ambari-server ) to all machines in the cluster , &lt;/P&gt;&lt;P&gt;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   &lt;/P&gt;</description>
      <pubDate>Thu, 23 Nov 2017 21:44:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/ambari-Standby-NameNode-not-started/m-p/201521#M71659</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-11-23T21:44:32Z</dc:date>
    </item>
  </channel>
</rss>

