Multiple students reported that during cm hadoop deploy, when it goes to ansible all -m ping -u ubuntu, log reports UNREACHABLE when there is no network issue at all. Each node can be log in manually.
(ENV) mike@mike:~$ cm hadoop deploy
Cluster cluster-002 is now active
Cluster cluster-002 created
DEBUG: Loading BigDataStack to /home/mike/.cloudmesh/stacks/stack-001/.cloudmesh_metadata
DEBUG: Calling mk-inventory in /home/mike/.cloudmesh/stacks/stack-001
DEBUG: Running cmd: python mk-inventory -n stack-001 129.114.33.138 129.114.33.59 129.114.33.5
DEBUG: Writing inventory file
DEBUG:
[namenodes]
stack-0010
[resourcemanagernodes]
stack-0010
[monitornodes]
stack-0010
[datanodes]
stack-0010
stack-0011
stack-0012
[zookeepernodes]
stack-0010
[hadoopnodes]
stack-0010
stack-0011
stack-0012
[historyservernodes]
stack-0010
[journalnodes]
stack-0010
[frontendnodes]
stack-0010
INFO: Waiting for cluster to be accessible
DEBUG: Running cmd: ansible all -m ping -u ubuntu
stack-0011 | UNREACHABLE! => {
"changed": false,
"msg": "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
}
stack-0012 | UNREACHABLE! => {
"changed": false,
"msg": "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
}
stack-0010 | UNREACHABLE! => {
"changed": false,
"msg": "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
}
Multiple students reported that during cm hadoop deploy, when it goes to
ansible all -m ping -u ubuntu, log reports UNREACHABLE when there is no network issue at all. Each node can be log in manually.(ENV) mike@mike:~$ cm hadoop deploy Cluster cluster-002 is now active Cluster cluster-002 created DEBUG: Loading BigDataStack to /home/mike/.cloudmesh/stacks/stack-001/.cloudmesh_metadata DEBUG: Calling mk-inventory in /home/mike/.cloudmesh/stacks/stack-001 DEBUG: Running cmd: python mk-inventory -n stack-001 129.114.33.138 129.114.33.59 129.114.33.5 DEBUG: Writing inventory file DEBUG: [namenodes] stack-0010
[resourcemanagernodes] stack-0010
[monitornodes] stack-0010
[datanodes] stack-0010 stack-0011 stack-0012
[zookeepernodes] stack-0010
[hadoopnodes] stack-0010 stack-0011 stack-0012
[historyservernodes] stack-0010
[journalnodes] stack-0010
[frontendnodes] stack-0010
INFO: Waiting for cluster to be accessible DEBUG: Running cmd: ansible all -m ping -u ubuntu stack-0011 | UNREACHABLE! => { "changed": false, "msg": "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 } stack-0012 | UNREACHABLE! => { "changed": false, "msg": "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 } stack-0010 | UNREACHABLE! => { "changed": false, "msg": "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 }