<?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: The DataNode is not connected to one or more of its NameNode(s). in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/The-DataNode-is-not-connected-to-one-or-more-of-its-NameNode/m-p/45199#M46134</link>
    <description>&lt;P&gt;Hello Karthi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for bringing your questions to this community.&lt;/P&gt;&lt;P&gt;I'll start by saying that the health issues you see stem from an inability for the Cloudera Manager agents on your host/hosts to communicate with Cloudera Manager on port 7182 and for your agent to communicate with the Host Monitor (to upload metrics) on port 9995.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It could be your agent is not started. &amp;nbsp;On your host or hosts, try running (as root or sudo):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;service cloudera-scm-agent start&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you are lucky, that's all that needs to be done. &amp;nbsp;If the agents are running and you still see this problem, this gets into more complex troubleshooting. &amp;nbsp;In that case, I'd start by making sure that iptables is not restricting ports (turn it off on all hosts if it is on), try telneting or nc to the Cloudera Manager host's port 7182.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All that said, you may want to walk our quickstart tutorial here:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;&lt;A href="http://www.cloudera.com/developers/get-started-with-hadoop-tutorial.html" target="_blank"&gt;http://www.cloudera.com/developers/get-started-with-hadoop-tutorial.html&lt;/A&gt;&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;It might probe to be a good start since you are new to Cloudera and hadoop.&lt;/P&gt;&lt;P class="p1"&gt;We love that you are giving this a try so keep the questions coming.&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;NOTE: &amp;nbsp;for troubleshooting agent issues, your best friend is the agent log; by default it is:&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;/var/log/cloudera-scm-agent/cloudera-scm-agent.log&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;Look for python stack traces and error messages that could help you and us diagnose the issue.&lt;/P&gt;&lt;P class="p1"&gt;By default, the agent will try to heartbeat to the server that is configured in the "server_host" configuration in the agent's configurtation file ( /etc/cloudera-scm-agent/config.ini ). &amp;nbsp;So make sure that the host is that of your Cloudera Manager and it is resolvable on this host.&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;That's a lot, so I'll stop there. &amp;nbsp;Let us know if you get stuck.&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;Cheers,&lt;/P&gt;&lt;P class="p1"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p1"&gt;Ben&lt;/P&gt;</description>
    <pubDate>Fri, 16 Sep 2016 17:23:03 GMT</pubDate>
    <dc:creator>bgooley</dc:creator>
    <dc:date>2016-09-16T17:23:03Z</dc:date>
  </channel>
</rss>

