- Welcome BMC Customer Support Site Guest User
Knowledge Article
Kafka and Zookeeper services fail to start in Control-M/Enterprise Manager or Control-M/Server version 9.0.21 in a new Windows cluster installation, after a cluster failover or move is performed
Control-M/Enterprise Manager
Control-M/Enterprise Manager
Control-M/Enterprise Manager ; Control-M/Server ; version 9.0.21 ; Windows cluster
A new installation of either Control-M/Enterprise Manager or Control-M/Server version 9.0.21 on Windows in a cluster fails to add Kafka and Zookeeper services to the resource group and as a result when a failover or move is performed to switch the active node of the cluster, the Kafka and Zookeeper services do not behave properly |
Control-M fails to add Kafka and Zookeeper services to the Windows resource group
This issue is targeted to be resolved in version 9.0.21.100 (subject to change) Use the following steps after the installation to prevent the Kafka/Zookeeper startup failure until the issue is resolved 1) Stop all Control-M/Enterprise Manager and/or Control-M/Server Cluster resources via the Windows Cluster Manager 2) Verify no Control-M/Enterprise Manager and/or Control-M/Server processes are running If necessary kill process that are still running 3) Open a Powershell session and execute the following: For Control-M/Enterprise Manager : cd "<EM_HOME>\bin"
.\CTMUpadteCluster_V21.ps1 install EM For Control-M/Server :
cd "<CTM_HOME>\scripts"
.\CTMUpdateCluster_V21.ps1 install CTM 4) Restart the Cluster manager service on ALL cluster nodes. Open a command prompt and execute the following:
net stop clussvc && net start clussvc
5) Start all Control-M/Enterprise Manager and/or Control-M/Server resources from the cluster manager 6) Set the Control-M Web Server Desired State to "Ignored". For Control-M/Enterprise Manager, run the following command:
em updater -cluster_components 9.0.21.000
For Control-M/Server
No action is required |
Attachment(s):