I have a an existing HDP 2.4 cluster with below mentioned details. node1 & node2 are masters in HA setup node3, 4, 5, 6 are datanodes node1, 2, 3 are journal nodes node4, 5, 6 are zookeeper nodes node7 is Ambari server node12 is client node 8, 9, 10, 11 are metron nodes (search, web & installer) Services Node1: Namenode, History Server, Resource Manager, Timeline Server Node2: HBase Master, Storm UI, Spark History, DRPC, Nimbu, Graphana, Nfs Gateway, Hive Server, Hive Metastore, WebHCat, Hive client Node3-6: Datanode, Kafka broker, Region Server, NodeManager, Supervisor Node7: Ambari server Node12: HDFS Client, MR2 Client, YARN Client, Zookeeper Client, Tez Client, HCat Client, Pig Client, HBase Client, Sqoop Client Node7: Netflow / YAF probe, BRO probe, SNORT probe, PCAP probe Node8 & Node9: Metron Search Node10: Metron Web Node11: Metron Installer I get the below error while issuing ansible-playbook command. [root@2da14a90fa00 playbooks]# ansible-playbook -i /root/incubator-metron/metron-deployment/inventory/$INSTALL_CONF_DIRECTORY metron_install.yml --skip-tags="solr"
PLAY ***************************************************************************
skipping: no hosts matched
PLAY ***************************************************************************
skipping: no hosts matched
PLAY ***************************************************************************
TASK [setup] *******************************************************************
fatal: [node1]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [node8]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [node6]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [node7]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [node3]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [node4]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [node11]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [node10]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [node5]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [node9]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
fatal: [node12]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
TASK [setup] *******************************************************************
fatal: [node2]: UNREACHABLE! => {"changed": false, "msg": "ERROR! SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY RECAP *********************************************************************
node1 : ok=0 changed=0 unreachable=1 failed=0
node10 : ok=0 changed=0 unreachable=1 failed=0
node11 : ok=0 changed=0 unreachable=1 failed=0
node12 : ok=0 changed=0 unreachable=1 failed=0
node2 : ok=0 changed=0 unreachable=1 failed=0
node3 : ok=0 changed=0 unreachable=1 failed=0
node4 : ok=0 changed=0 unreachable=1 failed=0
node5 : ok=0 changed=0 unreachable=1 failed=0
node6 : ok=0 changed=0 unreachable=1 failed=0
node7 : ok=0 changed=0 unreachable=1 failed=0
node8 : ok=0 changed=0 unreachable=1 failed=0
node9 : ok=0 changed=0 unreachable=1 failed=0 [root@node11 scripts]# ./platform-info.sh Metron 0.2.0BETA
fatal: Not a git repository (or any of the parent directories): .git
-- ansible 2.0.0.2 config file = configured module search path = Default w/o overrides --
./platform-info.sh: line 52: vagrant: command not found
-- Python 2.6.6
-- Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T22:11:47+05:30) Maven home: /opt/apache-maven-3.3.9 Java version: 1.8.0_60, vendor: Oracle Corporation Java home: /opt/jdk1.8.0_60/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.32-573.el6.x86_64", arch: "amd64", family: "unix"
--
Linux node11.metron 2.6.32-573.el6.x86_64 #1 SMP Thu Jul 23 15:44:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
... View more
