How to fix the SSH Key Errors with dcli on an Oracle BDA Hadoop Cluster
You may receive errors when using dcli to run commands over SSH on the BDA nodes, such as the following:
[root@mybda1r01s02 ~]# dcli date -
The authenticity of host '10.152.250.208 (10.152.250.208)' can't be established.
RSA key fingerprint is 17:3c:32:3d:b8:6a:2c:af:7f:16:88:f2:25:ec:6c:31.
Are you sure you want to continue connecting (yes/no)? The authenticity of host '10.152.250.212 (10.152.250.212)' can't be established.
RSA key fingerprint is 2f:14:40:5c:56:f7:72:a8:45:35:1f:91:a6:8a:ae:f9.
Are you sure you want to continue connecting (yes/no)? The authenticity of host '10.152.250.211 (10.152.250.211)' can't be established.
RSA key fingerprint is fd:b6:6a:c1:57:5b:e2:c6:f5:8f:9f:5f:dc:04:1d:81.
This error simply means the the SSH keys are not in the known_hosts file on the nodes. You can force dcli to accept the keys by running:
dcli -s '-o StrictHostKeyChecking=no' date
Thereafter you should be able to run dcli without receiving these error messages.
Note: in order to setup passwordless SSH follow the instructions outlined in the BDA documentation linked to below.
https://docs.oracle.com/cd/E37231_01/doc.20/e36962/dcli.htm#BIGOG76616
The error messages may be shown if passwordless SSH has been setup manually instead of using the Oracle provide setup-root-ssh script. In this case, you may find that after using the StrictHostKeyChecking SSH option mentioned above dcli works but prompts you for a password. This can be fixed by running
setup-root-ssh -p <replace with actual root password>
[root@mybda1r01s02 ~]# dcli date -
The authenticity of host '10.152.250.208 (10.152.250.208)' can't be established.
RSA key fingerprint is 17:3c:32:3d:b8:6a:2c:af:7f:16:88:f2:25:ec:6c:31.
Are you sure you want to continue connecting (yes/no)? The authenticity of host '10.152.250.212 (10.152.250.212)' can't be established.
RSA key fingerprint is 2f:14:40:5c:56:f7:72:a8:45:35:1f:91:a6:8a:ae:f9.
Are you sure you want to continue connecting (yes/no)? The authenticity of host '10.152.250.211 (10.152.250.211)' can't be established.
RSA key fingerprint is fd:b6:6a:c1:57:5b:e2:c6:f5:8f:9f:5f:dc:04:1d:81.
This error simply means the the SSH keys are not in the known_hosts file on the nodes. You can force dcli to accept the keys by running:
dcli -s '-o StrictHostKeyChecking=no' date
Thereafter you should be able to run dcli without receiving these error messages.
Note: in order to setup passwordless SSH follow the instructions outlined in the BDA documentation linked to below.
https://docs.oracle.com/cd/E37231_01/doc.20/e36962/dcli.htm#BIGOG76616
The error messages may be shown if passwordless SSH has been setup manually instead of using the Oracle provide setup-root-ssh script. In this case, you may find that after using the StrictHostKeyChecking SSH option mentioned above dcli works but prompts you for a password. This can be fixed by running
setup-root-ssh -p <replace with actual root password>
Comments
Post a Comment