FAQ
I have successfully installed CDH4 on Amazan EC2. It was working fine. I
stopped the instance from EC2 to save costs and restarted later from EC2.
Then I restarted all services from Cloudera manager, and deployed client
configurations. However, Hadoop is not working:

  Call From ip-10-147-146-227.ec2.internal/10.147.146.227 to
ip-10-147-146-227.ec2.internal:8020 failed on connection exception:
java.net.ConnectException: Connection refused; For more details see:
  http://wiki.apache.org/hadoop/ConnectionRefused

Please help.

Thanks.
Sassoon Kosian

Search Discussions

  • Sassoon Kosian at Jul 1, 2013 at 6:00 pm
    Let me add also that the internal IP hasn't changed. I also added this line
    to /etc/hosts file:

    ip-10-147-146-227.ec2.internal ubuntu

    On Mon, Jul 1, 2013 at 1:56 PM, Sassoon Kosian wrote:

    I have successfully installed CDH4 on Amazan EC2. It was working fine. I
    stopped the instance from EC2 to save costs and restarted later from EC2.
    Then I restarted all services from Cloudera manager, and deployed client
    configurations. However, Hadoop is not working:

    Call From ip-10-147-146-227.ec2.internal/10.147.146.227 to
    ip-10-147-146-227.ec2.internal:8020 failed on connection exception:
    java.net.ConnectException: Connection refused; For more details see:
    http://wiki.apache.org/hadoop/ConnectionRefused

    Please help.

    Thanks.
    Sassoon Kosian


    --
    Sassoon Kosian Art <http://www.sassoonkosian.com>
  • Sassoon Kosian at Jul 1, 2013 at 6:05 pm
    Let me add also that the internal IP hasn't changed. I also added this line
    to /etc/hosts file:

    ip-10-147-146-227.ec2.internal ubuntu
  • Harsh J at Jul 5, 2013 at 2:19 pm
    Am no AMZN services expert but are you positive you still have an NN
    running on host ip-10-147-146-227.ec2.internal port 8020? You could
    try telnet-ing to it.

    Alternatively, if the hostname has changed, try running "hostname"
    command on the NN box to get the new one and reconfigure the client's
    core-site.xml to point to it.
    On Mon, Jul 1, 2013 at 11:26 PM, Sassoon Kosian wrote:
    I have successfully installed CDH4 on Amazan EC2. It was working fine. I
    stopped the instance from EC2 to save costs and restarted later from EC2.
    Then I restarted all services from Cloudera manager, and deployed client
    configurations. However, Hadoop is not working:

    Call From ip-10-147-146-227.ec2.internal/10.147.146.227 to
    ip-10-147-146-227.ec2.internal:8020 failed on connection exception:
    java.net.ConnectException: Connection refused; For more details see:
    http://wiki.apache.org/hadoop/ConnectionRefused

    Please help.

    Thanks.
    Sassoon Kosian


    --
    Harsh J
  • Sassoon Kosian at Jul 22, 2013 at 11:01 pm
    The IP had indeed changed. I have followed these steps
    https://groups.google.com/a/cloudera.org/forum/?fromgroups=#!topic/scm-users/gM-DtmxvkJ8 and
    updated the internal ip address. But I am getting the same error with the
    new IP now. What else needs to be done?

    ls: Call From ip-10-80-215-107.ec2.internal/10.80.215.107 to
    ip-10-80-215-107.ec2.internal:8020 failed on connection exception:
    java.net.ConnectException: Connection refused; For more details see:
      http://wiki.apache.org/hadoop/ConnectionRefused


    BTW, telneting doesn't work on this one and even of a perfectly healthy
    running cluster. Looks like the problem is somewhere else as my other
    otherwise very similar cluster works fine though I can't telnet into it
    from anywhere.

    Thanks.
    Sassoon
    On Friday, July 5, 2013 10:19:05 AM UTC-4, Harsh J wrote:

    Am no AMZN services expert but are you positive you still have an NN
    running on host ip-10-147-146-227.ec2.internal port 8020? You could
    try telnet-ing to it.

    Alternatively, if the hostname has changed, try running "hostname"
    command on the NN box to get the new one and reconfigure the client's
    core-site.xml to point to it.
    On Mon, Jul 1, 2013 at 11:26 PM, Sassoon Kosian wrote:
    I have successfully installed CDH4 on Amazan EC2. It was working fine. I
    stopped the instance from EC2 to save costs and restarted later from EC2.
    Then I restarted all services from Cloudera manager, and deployed client
    configurations. However, Hadoop is not working:

    Call From ip-10-147-146-227.ec2.internal/10.147.146.227 to
    ip-10-147-146-227.ec2.internal:8020 failed on connection exception:
    java.net.ConnectException: Connection refused; For more details see:
    http://wiki.apache.org/hadoop/ConnectionRefused

    Please help.

    Thanks.
    Sassoon Kosian


    --
    Harsh J
  • Sassoon Kosian at Jul 22, 2013 at 11:07 pm
    I forgot to mention that I did reconfigure core-site.xml as well
    as hdfs-site.xml with the new internal IP.
    On Monday, July 22, 2013 7:01:03 PM UTC-4, Sassoon Kosian wrote:

    The IP had indeed changed. I have followed these steps
    https://groups.google.com/a/cloudera.org/forum/?fromgroups=#!topic/scm-users/gM-DtmxvkJ8 and
    updated the internal ip address. But I am getting the same error with the
    new IP now. What else needs to be done?

    ls: Call From ip-10-80-215-107.ec2.internal/10.80.215.107 to
    ip-10-80-215-107.ec2.internal:8020 failed on connection exception:
    java.net.ConnectException: Connection refused; For more details see:
    http://wiki.apache.org/hadoop/ConnectionRefused


    BTW, telneting doesn't work on this one and even of a perfectly healthy
    running cluster. Looks like the problem is somewhere else as my other
    otherwise very similar cluster works fine though I can't telnet into it
    from anywhere.

    Thanks.
    Sassoon
    On Friday, July 5, 2013 10:19:05 AM UTC-4, Harsh J wrote:

    Am no AMZN services expert but are you positive you still have an NN
    running on host ip-10-147-146-227.ec2.internal port 8020? You could
    try telnet-ing to it.

    Alternatively, if the hostname has changed, try running "hostname"
    command on the NN box to get the new one and reconfigure the client's
    core-site.xml to point to it.

    On Mon, Jul 1, 2013 at 11:26 PM, Sassoon Kosian <sko...@gmail.com>
    wrote:
    I have successfully installed CDH4 on Amazan EC2. It was working fine. I
    stopped the instance from EC2 to save costs and restarted later from EC2.
    Then I restarted all services from Cloudera manager, and deployed client
    configurations. However, Hadoop is not working:

    Call From ip-10-147-146-227.ec2.internal/10.147.146.227 to
    ip-10-147-146-227.ec2.internal:8020 failed on connection exception:
    java.net.ConnectException: Connection refused; For more details see:
    http://wiki.apache.org/hadoop/ConnectionRefused

    Please help.

    Thanks.
    Sassoon Kosian


    --
    Harsh J

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedJul 1, '13 at 5:56p
activeJul 22, '13 at 11:07p
posts6
users2
websitecloudera.com
irc#hadoop

2 users in discussion

Sassoon Kosian: 5 posts Harsh J: 1 post

People

Translate

site design / logo © 2022 Grokbase