Home Forums HDP on Linux – Installation single node

This topic contains 3 replies, has 2 voices, and was last updated by  Sasha J 1 year, 10 months ago.

  • Creator
    Topic
  • #11875

    vik onto
    Member

    hi
    I cannot add node to my single node cluster
    I did all that you recommended in documentation and in forum , but anyway failed with :

    Permission denied, please try again.
    Permission denied, please try again.
    Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).

    I run the check.sh and put it on ftp.
    vik_my_out_for_HMC.txt
    pls help me :)

    ————–
    System check results:
    Tue Nov 6 18:45:42 IST 2012
    Cluster name: mySingleCluster
    Total number of nodes: 1
    HMC nodename: mydvm1067.devlab.ad
    HMC node IP address: mydvm1067.devlab.ad

    =========== Node mydvm1067.devlab.ad ===========
    1. Hosts table
    16.55.246.233 mydvm1067.devlab.ad MYDVM1067

    2. Full host name
    mydvm1067.devlab.ad

    3. Kernel and architecture
    Linux MYDVM1067 2.6.32-279.11.1.el6.x86_64 #1 SMP Sat Sep 22 07:10:26 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

    4. OS version
    Red Hat Enterprise Linux Server release 6.3 (Santiago)
    Kernel \r on an \m

    5. Running networks
    eth0 Link encap:Ethernet HWaddr 00:50:56:9F:6E:45
    inet addr:16.55.246.233 Bcast:16.55.247.255 Mask:255.255.252.0
    inet6 addr: 2620:0:a17:e00e:250:56ff:fe9f:6e45/64 Scope:Global
    inet6 addr: fe80::250:56ff:fe9f:6e45/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:7654257 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1674842 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1992152333 (1.8 GiB) TX bytes:1734912999 (1.6 GiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:6894 errors:0 dropped:0 overruns:0 frame:0
    TX packets:6894 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1948051 (1.8 MiB) TX bytes:1948051 (1.8 MiB)

    virbr0 Link encap:Ethernet HWaddr 52:54:00:02:3D:08
    inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:5242 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:252437 (246.5 KiB)

    6. Firewall
    iptables: Firewall is not running.

    7. SELINUX
    SELinux status: disabled

    8. NTP
    ntpd is stopped

    9. Name resolution
    Server: 16.44.49.3
    Address: 16.44.49.3#53

    Name: mydvm1067.devlab.ad
    Address: 16.55.246.233

    10. Repositories list
    BTDT-LinuxCOE
    epel.repo
    epel-testing.repo
    hdp.repo
    remi.repo
    rhel-source.repo

    11. Partitions and mount-points
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/sda3 74316992 8825324 61716488 13% /
    tmpfs 4028964 288 4028676 1% /dev/shm
    /dev/sda1 198337 71590 116507 39% /boot
    mydastr01

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

You must be logged in to reply to this topic.

  • Author
    Replies
  • #11924

    Sasha J
    Moderator

    Vik,
    I’m sure you can connect to your single node cluster over ssh using hostname and localhost.
    But you are trying to add second node into it, right?
    This means that your ssh connectivity should also work same way to your second node.
    Make sure you can connect to the second from the first one.
    Also,
    please use script from this post:

    http://hortonworks.com/community/forums/topic/hmc-installation-support-help-us-help-you/

    and upload results as described.

    Thank you!
    Sasha

    Collapse
    #11921

    vik onto
    Member

    Hi Sasha
    it’s single node, and I can connect to localhost and hostname by ssh
    but stil cannot add node by web gui

    Collapse
    #11876

    Sasha J
    Moderator

    Vik,
    it seems like you ssh key is not propagated correctly to new node.
    You should use same key as you have on your original node on new one.
    your existing node should be able to ssh to new one with no password asking.

    Thank you!
    Sasha

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