When CMA_AGENT does not appear as a service type, install both Cloudera Migration Assistant CSD files on the Cloudera Manager Server host and restart Cloudera Manager Server.
Cause: One or both Cloudera Migration Assistant CSD
files (CMA_MASTER and CMA_AGENT) are not installed, or
Cloudera Manager was not restarted after CSD installation.
For end-to-end parcel installation, see Deploying the CMA server with parcels.
-
Download both CSD JAR files to /opt/cloudera/csd/ on the Cloudera Manager Server host.
wget -P /opt/cloudera/csd/ https://archive.cloudera.com/cma/version/csd/CMA_MASTER-version-build.jar
wget -P /opt/cloudera/csd/ https://archive.cloudera.com/cma/version/csd/CMA_AGENT-version-build.jar
-
Set ownership.
chown cloudera-scm:cloudera-scm /opt/cloudera/csd/CMA_MASTER-version-build.jar /opt/cloudera/csd/CMA_AGENT-version-build.jar
-
Set permissions.
chmod 640 /opt/cloudera/csd/CMA_MASTER-version-build.jar /opt/cloudera/csd/CMA_AGENT-version-build.jar
-
Restart the Cloudera Manager Server.
systemctl restart cloudera-scm-server
-
Wait for Cloudera Manager to restart (approximately 90–120 seconds),
then verify that the CMA service types are
available.
