As this is only CM installation completed but no CDH cluster created already, it may be simpler to just start with an empty database for CM (and CMS services where needed) instead of migrating the current database. See instructions provided in the product documentation ... View more

Thanks for reporting back the root cause you've found! ... View more

Please set "-Xmx4G" in  /etc/default/cloudera-scm-server and restart CM, then test again. The apparent deadlock messages are an indicator of low memory condition and misleading, we need to make sure to cover the most likely root causes first.   ... View more

Please review the CM API docs  for CM 5.x http://cloudera.github.io/cm_api/apidocs/v19/index.html for CM 6.x https://archive.cloudera.com/cm6/6.2.0/generic/jar/cm_api/apidocs/index.html Posting a role object will make CM create that role e.g. http://cloudera.github.io/cm_api/apidocs/v19/path__clusters_-clusterName-_services_-serviceName-_roles.html   You may want to look into this end-to-end example in python as well. ... View more

Please review the sections in the Monitoring and Diagnostics documentation chapter. ... View more

CM commands (e.g. restart a role on a cluster node) time out after 150 seconds if there is no response sent back during this time. This happens e.g. if the CM agent on the cluster node is not heartbeating into CM server. Please increase heap memory for CM server in /etc/default/cloudera-scm-server (to avoid the apparent deadlock issue which indicates out of memory condition) make sure that all hosts are in good health state and heartbeating in in CM -> Hosts -> All Hosts page (the "Last Heartbeat" value needs to be lower than 15 seconds) If the host is not heartbeating in then the restart command will fail. The CM agent logs will hopefully show details, a quick resolution may be to restart the CM agent on that node with command  # service cloudera-scm-agent restart ... View more

Hi Nick,   you may want to have a look into the code at https://github.com/gdgt/cmapi This also covers sqoop installation and configuration ... View more

Can you please copy the output of the following commands to here, to clarify the permissions problem:   # namei -l /var/log/cloudera-scm-server/cloudera-scm-server.out # namei -l /var/run/cloudera-scm-server.pid ... View more

Please restart the service with root privileges e.g.  # sudo service cloudera-scm-server restart Note that force_start has a different purpose than helping over permissions issues. ... View more

Just enter the corresponding OU's where users or groups are found. Please make sure that setting are correct and allow users and it's member groups can be found in LDAP. We suggest to test your settings using the jmldap.jar tool first, for ease of testing and debugging. ... View more

The Linux kernel does the responsible for swapping in/out memory pages. First step needs to find out if this swapping is due to memory pressure or if there is sufficient system memory avaiable at the time when the swap alert is shown. Please review top output at this time. ... View more

@JoaquinS Your CM agent config file does not have TLS enabled, but the CM server configuration has.  I would suggest to disable the  Use TLS Encryption for Agents, Use TLS Authentication of Agents to Server, Verify Agent Hostname Against Certificate settings and restart CM to proceed to make the installation work in a first step.   Once that is done, please follow the steps in this documentation chapter to enable TLS encryption for CM agent communication. ... View more

There is no option to run a script during/after a service restart in Cloudera Manager. A possible alternative way may be to poll the service status using CM API in your script, then act on changes.    Just out of interest, what is this script supposed to do? ... View more

In the screenshot none of the roles start up, and the startup command is timing out after 150 seconds (default behavior). This indicates a more generic problem.   Please check if host "node1" is in good health state in on the CM -> Hosts -> All Hosts page. Also verify on this page if the "Last Heartbeat" column shows a value less than 15 seconds.   Is this a new installation, or was this working fine before? Have you been able to start up any other services, e.g. Cloudera Management Service? ... View more

There is no option to dynamically set options. Please explain what parameter you want to set explicitly to what value, and why this is needed. ... View more

You may want to review if the Service Monitor has been restarted or is unoperable. To keep the Impala queries for a longer time, please increase the Impala queries store maximum size ... View more

If you switched from using ntp to using chrony service then please restart the CM agent on all cluster nodes. This should help with the clock offset related issues.   For roles with health alert This role's process exited please review the stdout, stderr and role logs to find out details why the startup failed, those are found in /var/run/cloudera-scm-agent/process directory, lookup e.g. the recent directories for Spark and review the stdout/stderr logs for error messages. ... View more

Misunderstanding here, note the document explicitly references upgrade to Cloudera Manager 6.0. That was a restriction for CM 6.0 but since CM 6.1 you can upgrade straight from CM 5.16 to 6.1.0. ... View more