<?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: data nodes can't reach name node in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/data-nodes-can-t-reach-name-node/m-p/86057#M2865</link>
    <description>&lt;P&gt;for my case I was just working on cloudera VM , I had to configure the node ip ,&lt;BR /&gt;=&amp;gt; ifconfig LOCAL_NODE_IP eth1:2 netmask XXXX&lt;BR /&gt;after that pinging to that ip is going well&lt;BR /&gt;thanks a lot&lt;/P&gt;</description>
    <pubDate>Thu, 07 Feb 2019 13:53:39 GMT</pubDate>
    <dc:creator>Bildervic</dc:creator>
    <dc:date>2019-02-07T13:53:39Z</dc:date>
    <item>
      <title>data nodes can't reach name node</title>
      <link>https://community.cloudera.com/t5/Support-Questions/data-nodes-can-t-reach-name-node/m-p/21174#M2862</link>
      <description>&lt;P&gt;My data nodes in my new cloudera live cluster seem unable to reach the master node. I've tried restarting HDFS several times from Cloudera Manager and I get the following error message:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"Command aborted because of exception: Command timed-out after 150 seconds"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can login to each machine using root and the passwords provided on the gogrid page. Should ssh be set up between these machines to not require entering a password? I'm not sure if I missed a step in the configuration or if it should be done automatically when the cluster is first deployed; of course it could be some other connectivity problem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think the following is a symptom of the same connectivity problem. If I ssh to one of the data nodes (I anonymized part of the hostname) and try to run this command, I get this error:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[root@XXXXX-cldraagent-01 ~]# hadoop fs -ls /user/hue&lt;BR /&gt;ls: No Route to Host from XXXXX-cldraagent-01/10.NNN.NNN.3 to XXXXX-cldramaster-01:8020 failed on socket timeout exception: java.net.NoRouteToHostException: No route to host; For more details see: &lt;A href="http://wiki.apache.org/hadoop/NoRouteToHost" target="_blank"&gt;http://wiki.apache.org/hadoop/NoRouteToHost&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can ping the master from the agent (again anonymizing):&lt;/P&gt;&lt;P&gt;ping XXXXX-cldramaster-01&lt;BR /&gt;PING XXXXX-cldramaster-01 (10.NNN.NNN.2) 56(84) bytes of data.&lt;BR /&gt;64 bytes from XXXXX-cldramaster-01 (10.NNN.NNN.2): icmp_seq=1 ttl=64 time=0.276 ms&lt;BR /&gt;64 bytes from XXXXX-cldramaster-01 (10.NNN.NNN.2): icmp_seq=2 ttl=64 time=0.358 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Appreciate any pointers, and apologies if this is a stupid question&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 09:11:46 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/data-nodes-can-t-reach-name-node/m-p/21174#M2862</guid>
      <dc:creator>CentralNJ2014</dc:creator>
      <dc:date>2022-09-16T09:11:46Z</dc:date>
    </item>
    <item>
      <title>Re: data nodes can't reach name node</title>
      <link>https://community.cloudera.com/t5/Support-Questions/data-nodes-can-t-reach-name-node/m-p/21231#M2863</link>
      <description>&lt;P&gt;For what it's worth in case somebody else encounters a similar problem, after adding ssh keys I had the same problem but I found the following instructions:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="http://www.cyberciti.biz/tips/no-route-to-host-error-and-solution.html"&gt;http://www.cyberciti.biz/tips/no-route-to-host-error-and-solution.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ran these commands on the master (name node), and now hdfs is working properly on all 4 nodes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;/sbin/iptables -L -n&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;/etc/init.d/iptables save&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;/etc/init.d/iptables stop&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier;"&gt;/sbin/iptables -L -n&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2014 15:43:50 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/data-nodes-can-t-reach-name-node/m-p/21231#M2863</guid>
      <dc:creator>CentralNJ2014</dc:creator>
      <dc:date>2014-11-05T15:43:50Z</dc:date>
    </item>
    <item>
      <title>Re: data nodes can't reach name node</title>
      <link>https://community.cloudera.com/t5/Support-Questions/data-nodes-can-t-reach-name-node/m-p/53301#M2864</link>
      <description>&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2017 21:32:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/data-nodes-can-t-reach-name-node/m-p/53301#M2864</guid>
      <dc:creator>AdminHbd</dc:creator>
      <dc:date>2017-04-06T21:32:28Z</dc:date>
    </item>
    <item>
      <title>Re: data nodes can't reach name node</title>
      <link>https://community.cloudera.com/t5/Support-Questions/data-nodes-can-t-reach-name-node/m-p/86057#M2865</link>
      <description>&lt;P&gt;for my case I was just working on cloudera VM , I had to configure the node ip ,&lt;BR /&gt;=&amp;gt; ifconfig LOCAL_NODE_IP eth1:2 netmask XXXX&lt;BR /&gt;after that pinging to that ip is going well&lt;BR /&gt;thanks a lot&lt;/P&gt;</description>
      <pubDate>Thu, 07 Feb 2019 13:53:39 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/data-nodes-can-t-reach-name-node/m-p/86057#M2865</guid>
      <dc:creator>Bildervic</dc:creator>
      <dc:date>2019-02-07T13:53:39Z</dc:date>
    </item>
  </channel>
</rss>

