After upgrading to version 9.0.20.200 where Control-M/Enterprise Manager and Control-M/Server are installed in different accounts on the same host or port 8080 is in use, Services in the CCM will show as initializing for one side or the other depending on which was started last. When reviewing the $HOME/kafka/kafka_data/log/zookeeper_server.log in either the Control-M/Enterprise Manager or Control-M/Server directory, it shows messages like the following: [2021-11-13 09:07:17,226] ERROR Unable to start AdminServer, exiting abnormally (org.apache.zookeeper.server.ZooKeeperServerMain) org.apache.zookeeper.server.admin.AdminServer$AdminServerException: Problem starting AdminServer on address 0.0.0.0, port 8080 and command URL /commands . . Caused by: java.io.IOException: Failed to bind to /0.0.0.0:8080 . . Caused by: java.net.BindException: Address already in use |
Edit the Zookeeper configuration for both Control-M/Enterprise Manager and Control-M/Server. NOTE: When editing the bmc.zookeeper.properties file below, make sure that there are no blank lines at the end of the file. The newly added line must be the last line. Control-M/Enterprise Manager: 1) Login as the Control-M/Enterprise Manager user 2) Navigate to $HOME/kafka/kafka_data/kafkadata/config 3) Make a backup copy of the bmc.zookeeper.properties file with the command: cp bmc.zookeeper.properties bmc.zookeeper.properties.backup 4) Edit bmc.zookeeper.properties and at the bottom of the file add the following parameter: admin.enableServer=false 5) After saving the file, run the command: em emsca shutdown -f 6) Wait for several minutes for the processes to restart and use the new configuration. NOTE: The EM Configuration Agent must be running Control-M/Server: 1) Login as the Control-M/Server user 2) Navigate to $HOME/kafka/kafka_data/kafkadata/config 3) Make a backup copy of the bmc.zookeeper.properties file with the command: cp bmc.zookeeper.properties bmc.zookeeper.properties.backup 4) Edit bmc.zookeeper.properties and at the bottom of the file add the following parameter: admin.enableServer=false 5) After saving the file, run the command: ctmsca shutdown -f 6) Wait for several minutes for the processes to restart and use the new configuration. NOTE: The Control-M/Server Configuration Agent must be running The Control Configuration Manager (CCM) will now show Services for both Control-M/Enterprise Manager and Control-M/Server are running. |