My Oracle Support Banner

Mammoth Actions like Decommission Fail Setting up Password-less SSH on BDA Clusters with a Large Number of Cluster Hosts (Doc ID 2847312.1)

Last updated on JULY 20, 2024

Applies to:

Big Data Appliance Integrated Software - Version 4.14.0 to 5.2.0 [Release 4.10 to 5.0]
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, table name, company name, email, hostnames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

Mammoth actions (directly or via bdacli commands) fail setting up Password-less SSH.

1. mammoth commands raise an error like below:

Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password)
ERROR: Node "<HOSTNAME_IP_ADDRESS>" does not seem to have passwordless ssh configured. Please use setup-root-ssh (or setup-root-ssh -C if cluster-wide) first

2. Additional messages show:

a. A message that Password-less SSH is not set up.
For example:

INFO: Creating nodelist files ...
INFO: Checking if password-less ssh is set up
INFO: Executing checkRoot.sh on nodes /opt/oracle/BDAMammoth/bdaconfig/tmp/all_nodes #Step -1#
INFO: Checking if password-less ssh is set up
INFO: Executing checkRoot.sh on nodes /opt/oracle/BDAMammoth/bdaconfig/tmp/all_nodes #Step -1#
INFO: Password-less SSH not set up, skipping reboot check

b. A message that there is "Error code 1" executing checkSSHAllNodes.sh.
For example:

INFO: Error code 1 when executing checkSSHAllNodes.sh on host <HOSTNAMEx>
INFO: Error is : Password-less ssh is not set up from node <HOSTNAMEx>
INFO: Error code 1 when executing checkSSHAllNodes.sh on host <HOSTNAMEa>
INFO: Error is : Password-less ssh is not set up from node <HOSTNAMEx>
INFO: Error code 1 when executing checkSSHAllNodes.sh on host <HOSTNAMEb>
INFO: Error is : Password-less ssh is not set up from node <HOSTNAMEx>
INFO: Error code 1 when executing checkSSHAllNodes.sh on host <HOSTNAMEc>
INFO: Error is : Password-less ssh is not set up from node <HOSTNAMEx>
...

c. Other "Permission denied" messages like:

INFO: Executing checkSSHAllNodes.sh on nodes /opt/oracle/BDAMammoth/bdaconfig/tmp/all_nodes #Step -1#
INFO: Error code 1 when executing checkSSHAllNodes.sh on host <HOSTNAME>
INFO: Error is : Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password)

And for each host, there is an associated .err file in /opt/oracle/BDAMammoth/bdaconfig/tmp/checkSSHAllNodes.sh_<HOSTNAME>.err containing:

Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password)

d. A message that authenticity of a host can't be established.
For example:

The authenticity of host <HOSTNAME> can't be established
ECDSA key fingerprint is ......
ECDSA key fingerprint is ......
Are you sure you want to continue connecting (yes/no)?

e. The associated trc file contains messages like below:

Carp::croak('ERROR: Failed when creating tmp/cleaning ssh directory on nod...') called at /opt/oracle/bda/mamoth-5.1.0/bdaconfig/Linuxs_SetSSH.pm line 65
s_SSH:ErrorExit('Failed when creating tmp/cleaning ssh directory on nod...') called at /opt/oracle/bda/mamoth-5.1.0/bdaconfig/Linuxs_SetSSH.pm line 629
s_SetSSH::SetSSH('/opt/oracle/BDAMammoth/bdaconfig/tmp/all_nodes', '','Y', 'CODE(0x<HEX_ERROR_CODE>)') called at GridSteps.pm line 2277
GridSteps::setupSSHroot() called at GridSteps.pm line 15954
GridSteps::TestAndSetPwdLessSSH() called at GridSteps.pm line 10682
GridSteps::GetOtherPasswords('CM_ADMIN_PWD') called at GridSteps.pm line 9210
GridSteps::getSecurityInformationFromCM() called at /opt/oracle/BDAMammoth/bdaconfig/GridInst.pl line 172



Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.