BDA 4.11 Node Migration Fails on CleanupInstall at enable_cm_alerts Due to Multiple Cluster Restarts Failing with "Command 'Stop' failed for cluster 'clustername'"
(Doc ID 2535996.1)
Last updated on JULY 20, 2024
Applies to:
Big Data Appliance Integrated Software - Version 4.11.0 to 4.12.0 [Release 4.10]Linux x86-64
Symptoms
On BDA 4.11 node migration fails on the final CleanupInstall step with an error like:
************************************
Error [23486]: (//<HOSTNAME1>.<DOMAIN>//Stage[main]/Main/Node[default]/Exec[enable_cm_alerts]/returns) change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmalerts.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmalerts.out returned 1 instead of one of [0]
************************************
Error [23486]: (//<HOSTNAME1>.<DOMAIN>//Stage[main]/Main/Node[default]/Exec[enable_cm_alerts]/returns) change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmalerts.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmalerts.out returned 1 instead of one of [0]
************************************
1. /opt/oracle/BDAMammoth/bdaconfig/tmp/enablecmalerts.out reports lots of failures stopping the cluster like:
Operation failed
Result Message is: "Command 'Stop' failed for cluster '<CLUSTERNAME>'",
Result Message is: "Command 'Stop' failed for cluster '<CLUSTERNAME>'",
2. Checking in Cloudera Manager > All Recent Commands, shows numerous cluster restarts all failing with "Command 'Stop' failed for cluster '<CLUSTERNAME>'".
Changes
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 |