Mammoth Migration for the Host with Cloudera Manager Fails on Step 1, PreinstallChecks running verifyMySQLPasswd.sh with "ERROR 2003 (HY000): Can’t connect to MySQL server"
(Doc ID 2860823.1)
Last updated on JULY 20, 2024
Applies to:
Big Data Appliance Integrated Software - Version 4.13.0 and laterx86_64
Symptoms
NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, 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.
Performing a mammoth migration for the host with Cloudera Manager (CM) role, Node 3 by default following:
Node 3 Migration and Recommission on Oracle Big Data Appliance V4.11 and Higher (Doc ID 2524859.1)
or
Node 3 Migration and Reprovision on Oracle Big Data Appliance V4.1 OL6 Hadoop Cluster to Manage a Hardware Failure (Doc ID 1984854.1)
fails in Step 1, PreinstallChecks, with errors like below:
ERROR: Error code 1 when executing verifyMySQLPasswd.sh on host <HOSTNAME_TARGET_CMHOST> #Step 1#
ERROR: Error is : ERROR 2003 (HY000): Can’t connect to MySQL server on ‘<HOSTNAME_TARGET_CMHOST>’ (111) #Step 1#
ERROR: Error code 1 when executing verifyMySQLPasswd.sh on host <HOSTNAMEx> #Step 1#
ERROR: Error is : ERROR 2003 (HY000): Can’t connect to MySQL server on ‘<HOSTNAME_TARGET_CMHOST>’ (111) #Step 1#
...
ERROR: Error is : ERROR 2003 (HY000): Can’t connect to MySQL server on ‘<HOSTNAME_TARGET_CMHOST>’ (111) #Step 1#
ERROR: Error code 1 when executing verifyMySQLPasswd.sh on host <HOSTNAMEx> #Step 1#
ERROR: Error is : ERROR 2003 (HY000): Can’t connect to MySQL server on ‘<HOSTNAME_TARGET_CMHOST>’ (111) #Step 1#
...
Where verifyMySQLPasswd.sh contains:
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 |