My Oracle Support Banner

BDA Mammoth Patching fails with: Error code 1 when executing verifyMySQLPasswd.sh on host bdanode1, Access Denied (Doc ID 1995504.1)

Last updated on DECEMBER 04, 2019

Applies to:

Big Data Appliance Integrated Software - Version 4.1.0 and later
Linux x86-64

Symptoms

 

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, password values, 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.

 

Applying a BDA patch (could also be upgrade or running the cluster verifications with "./mammoth -c" ) with Mammoth fails as below after being prompted for and entering the MySQL 'root' password.

Enter password:
Enter password again:
INFO: Executing verifyMySQLPasswd.sh on nodes /opt/oracle/BDAMammoth/bdaconfig/tmp/all_nodes #Step -1#
ERROR: Error code 1 when executing verifyMySQLPasswd.sh on host bdanode01 #Step -1#
ERROR: Error is : Error 1045 (28000): Access denied for user 'root'@'bdanode01.example.com' (using password: YES) #Step -1#
...
ERROR: Error code 1 when executing verifyMySQLPasswd.sh on host bdanode0n #Step -1#
ERROR: Error is : Error 1045 (28000): Access denied for user 'root'@'bdanode0n.example.com' (using password: YES) #Step -1#
...
ERROR: Errors executing verifyMySQLPasswd.sh. Continuing anyway. #Step -1"
WARNING: Incorrect password.  Do you wish to try again? (yes/no):



Additional Symptoms:

1. On Node 1 of the cluster verifyMySQLPasswd.sh shows:

#!/bin/bash
echo show databases | /usr/bin/mysql -h bdanode03 -uroot -p'<MYSQL_ROOT_PASSWORD>'
echo show databases | /usr/bin/mysql -h bdanode02 -uroot -p'<MYSQL_ROOT_PASSWORD>'


Note: verifyMySQLPasswd.sh will be in a location under /opt/oracle/bda in a directory which represents the Mammoth activity like patch, upgrade, cluster validations for example like:

/opt/oracle/bda/install/log/patch-20744805/tmp-bdanode01/verifyMySQLPasswd.sh

2. Running verifyMySQLPasswd.sh directly indicates that the MySQL connection to Node 3 is successful, but the MySQL connection to Node 2 fails. 

Output from the script will be like:

Database
information_schema
BDA_ODI_REPO
BDA_STB
activity_monitor
hive
host_monitor
hue
mysql
navigator
navms
oozie
performance_schema
reports_manager
resource_manager
scm
sentry
service_monitor
ERROR 1045 (28000): Access denied for user 'root'@bdanode01.example.com' (using password: YES)

3. The associated verifyMySQLPasswd.sh_bdanode0x.err  and verifyMySQLPasswd.sh_bdanode0x.out files (located in the same directory as verifyMySQLPasswd.sh) show the same result.  For example:


a) verifyMySQLPasswd.sh_bdanode0x.out shows the same successful output from Node 3:

Database
information_schema
BDA_ODI_REPO
BDA_STB
activity_monitor
hive
host_monitor
hue
mysql
navigator
navms
oozie
performance_schema
reports_manager
resource_manager
scm
sentry
service_monitor


b) verifyMySQLPasswd.sh_bdanode0x.err shows the same error raised on Node 2:

ERROR 1045 (28000): Access denied for user 'root'@bdanode0x.example.com' (using password: YES)


4. Logging into MySQL on both Node 3 and Node 2 shows a different sets of passwords for 'root'@<HOSTNAME>.  The passwords in the MySQL database on Node 2 are incorrect.

a) On Node 3:

 

Changes

Applying a patch, upgrading, or running a cluster check with "./mammoth -c".

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
Changes
Cause
Solution


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