Home Forums HDP on Linux – Installation Failure registering new nodes

Tagged: 

This topic contains 4 replies, has 3 voices, and was last updated by  tedr 1 year, 7 months ago.

  • Creator
    Topic
  • #17276

    matt poirier
    Member

    I’m working with a fresh installation of CentOS 6 64bit and HortonWorks 1.2.1

    On my node i’m seeing this:
    INFO 2013-03-13 16:51:45,978 NetUtil.py:45 – DEBUG:: Connecting to the following url https://cl2r2c5n1.data.yieldex.com:8440/cert/ca
    INFO 2013-03-13 16:55:45,510 NetUtil.py:59 – Failed to connect to https://cl2r2c5n1.data.yieldex.com:8440/cert/ca due to [Errno 104] Connection reset by peer
    INFO 2013-03-13 16:55:45,510 NetUtil.py:78 – Server at https://cl2r2c5n1.data.yieldex.com:8440 is not reachable, sleeping for 10 seconds…
    INFO 2013-03-13 16:55:55,521 NetUtil.py:45 – DEBUG:: Connecting to the following url https://cl2r2c5n1.data.yieldex.com:8440/cert/ca
    INFO 2013-03-13 16:55:55,522 NetUtil.py:59 – Failed to connect to https://cl2r2c5n1.data.yieldex.com:8440/cert/ca due to [Errno 111] Connection refused
    INFO 2013-03-13 16:55:55,522 NetUtil.py:78 – Server at https://cl2r2c5n1.data.yieldex.com:8440 is not reachable, sleeping for 10 seconds…
    INFO 2013-03-13 16:56:05,532 NetUtil.py:45 – DEBUG:: Connecting to the following url https://cl2r2c5n1.data.yieldex.com:8440/cert/ca
    INFO 2013-03-13 16:56:05,533 NetUtil.py:59 – Failed to connect to https://cl2r2c5n1.data.yieldex.com:8440/cert/ca due to [Errno 111] Connection refused
    INFO 2013-03-13 16:56:05,534 NetUtil.py:78 – Server at https://cl2r2c5n1.data.yieldex.com:8440 is not reachable, sleeping for 10 seconds…
    INFO 2013-03-13 16:56:15,544 NetUtil.py:45 – DEBUG:: Connecting to the following url https://cl2r2c5n1.data.yieldex.com:8440/cert/ca
    ‘, None)

    STDERR
    Connection to cl2r2c5n2.data.yieldex.com closed.
    Registering with the server…

    on the master, i’m seeing this:
    17:43:24,501 INFO QueryImpl:152 – Executing resource query: {Host=null}
    17:43:24,501 INFO ClusterControllerImpl:92 – Using resource provider org.apache.ambari.server.controller.internal.HostResourceProvider for request type Host
    17:43:27,551 INFO QueryImpl:152 – Executing resource query: {Host=null}

    hostname -f on each machine:
    cl2r2c5n2.data.yieldex.com
    cl2r2c5n1.data.yieldex.com

    I have reinstalled both machines (fresh), I have rebooted both machines, I have removed/reinstalled ambari, I have added the hostnames to /etc/hosts, what other steps should I take. It’s behaving as if they just can’t talk to each other.

    Thanks

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

  • Author
    Replies
  • #17318

    tedr
    Member

    Hi Matt,

    Thanks for the update. It’s good to know that you’re up and running now.

    Thanks again,
    Ted.

    Collapse
    #17302

    matt poirier
    Member

    It appears we were bitten by this bug:

    https://issues.apache.org/jira/browse/AMBARI-1432

    It’s up and running now after upgrading to the DEV branch

    Thanks for the help

    Collapse
    #17283

    matt poirier
    Member

    Yes, I can telnet and connect to that port from the node.

    telnet cl2r2c5n1.data.yieldex.com 8440
    Trying 10.122.40.41…
    Connected to cl2r2c5n1.data.yieldex.com.
    Escape character is ‘^]’.

    It is pingable, it can resolve it with “host” and “nslookup” just fine the master is also set in /etc/hosts. Everything works except https connections to that port on the master.

    wget https://cl2r2c5n1.data.yieldex.com:8440
    –2013-03-13 18:59:41– https://cl2r2c5n1.data.yieldex.com:8440/
    Resolving cl2r2c5n1.data.yieldex.com… 10.122.40.41
    Connecting to cl2r2c5n1.data.yieldex.com|10.122.40.41|:8440… connected.
    (it times out after a while)

    Collapse
    #17279

    Seth Lyubich
    Keymaster

    Hi Matt,

    Looking on line from the log below it appears that there might be some problem with connection:

    Server at https://cl2r2c5n1.data.yieldex.com:8440 is not reachable

    Can you please make sure that cl2r2c5n1.data.yieldex.com is reachable from machine that you got this log from? Please make sure that network connection and name resolution works correctly on the cluster. You can try to ping the host.

    Please let us know if this is helpful.

    Thanks,
    Seth

    Collapse
Viewing 4 replies - 1 through 4 (of 4 total)