The link you provided will list all your replication schedules and their job result history.  If you know the replication schedule id (eg. below is id=5) perhaps using the replication/{id}/history endpoint [0] may help you. You can limit the history size by doing so.     http://cm-host.cloudera.com:7180/api/v17/clusters/Cluster%201/services/HDFS-1/replications/5/history?limit=1&offset=0   [0] https://cloudera.github.io/cm_api/apidocs/v17/path__clusters_-clusterName-_services_-serviceName-_replications_-scheduleId-_history.html     ... View more

Hi dekan,   It looks like you're running into the same issue as the following fellow community members [0] Can you try the workaround in [1]    [0] https://community.cloudera.com/t5/Cloudera-Manager-Installation/Cloudera-Manager-Heartbeat-Python-Supervisor-Issue-System-Exit/m-p/57547 [1] http://community.cloudera.com/t5/Cloudera-Manager-Installation/CDH-5-12-0-clouder-manager-agent-can-not-start/m-p/58726 ... View more

For posterity this seems to be an issue in CM 5.12 and a fix is scheduled to be available in CM 5.12.x maintenance release. - workaround posted in    [0] http://community.cloudera.com/t5/Cloudera-Manager-Installation/Installation-failed-Failed-to-receive-heartbeat-from-agent/m-p/58809#M11660 http://community.cloudera.com/t5/Cloudera-Manager-Installation/Cloudera-Manager-Agent-cannot-connect-with-supervisor-Failed-to/td-p/58522 http://community.cloudera.com/t5/Cloudera-Manager-Installation/CDH-5-12-0-clouder-manager-agent-can-not-start/m-p/58726 ... View more

hi leiyz,   can you share your mount output and also what does the following command show?   for mnt in $(mount|cut -d ' ' -f 3); do stat $mnt 1>/dev/null 2>&1; rc=$?; if [ $rc -ne 0 ]; then echo "error accessing $mnt"; fi; done regards,     michalis     ... View more

The mountpoint isn't part of Cloudera, and likely being mounted by other process in your system. The process that controls the tmpfs mount should be able to remount it again, however you will run into the issue again if you hard_stop the agent. The fix is already been committed and will be available in the next Cloudera maintenance release. ... View more

Hello Josholsan,   This stack trace [0] suggests that Cloudera Manager Agent failed to create '/var/run/cloudera-scm-agent/supervisor/supervisord.conf', from past experience the error is often misleading.    To assist us with troubleshooting;   On the affected node can you provide the output of the following command;   [bash prompt root-user]# /usr/lib/cmf/agent/build/env/bin/python /usr/lib/cmf/agent/build/env/bin/cmf-agent --package_dir /usr/lib/cmf/service --agent_dir /var/run/cloudera-scm-agent --lib_dir /var/lib/cloudera-scm-agent --logfile /var/log/cloudera-scm-agent/cloudera-scm-agent.log --comm_name cmf-agent --pidfile /var/run/cloudera-scm-agent/cloudera-scm-agent.pid   Best,   Michalis   [0]  >>[07/Aug/2017 10:25:17 +0000] 10429 MainThread agent ERROR Failed to connect to previous supervisor. >>Traceback (most recent call last): >> File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/agent.py", line 2109, in find_or_start_supervisor >> self.configure_supervisor_clients() >> File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.12.0-py2.7.egg/cmf/agent.py", line 2290, in configure_supervisor_clients >> supervisor_options.realize(args=["-c", os.path.join(self.supervisor_dir, "supervisord.conf")]) >> File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/options.py", line 1599, in realize >> Options.realize(self, *arg, **kw) >> File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/options.py", line 333, in realize >> self.process_config() >> File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/options.py", line 341, in process_config >> self.process_config_file(do_usage) >> File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/options.py", line 376, in process_config_file >> self.usage(str(msg)) >> File "/usr/lib/cmf/agent/build/env/lib/python2.7/site-packages/supervisor-3.0-py2.7.egg/supervisor/options.py", line 164, in usage >> self.exit(2) >>SystemExit: 2     ... View more

  Since you did not specify which approach, I had a python console open and below seems to return what may be looking for.     from cm_api.api_client import ApiResource api = ApiResource(server_host="cloudera-manager.host.com",version=12) cluster = api.get_cluster("___REPLACE_ME_WITH_CLUSTER_NAME__") for host in api.get_all_hosts(view='full'): # List (rolename,servicename,hostname) from all host where service name = impala print [(x.roleName,x.serviceName,host.hostname) for x in host.roleRefs if "impala" in str(x.serviceName).lower()]     ... View more

> I was away from my Cloudera cluster for a bit and the Enterprise trial expired in the mean time. When a Cloudera Enterprise license expires, the following occurs:  [0]     - Cloudera Enterprise Enterprise Data Hub Edition Trial - Enterprise features are no longer available. see Table [1] - Cloudera Enterprise - Cloudera Manager Admin Console displays a banner indicating license expiration. Contact Cloudera Support to receive an updated license. In the meanwhile, all enterprise features will continue to be available.   Is your CDH deployment packaged based or parcel?   Do you know what your yum update performed, if it updated any CDH/Cloudera packages? Can you check your yum logs /var/log/yum.log?   How did you determined that everything is _kaput_, is there any error/stack trace that you can share?   Best,   Michalis   [0] https://www.cloudera.com/documentation/enterprise/latest/topics/cm_ag_licenses.html#cmug_topic_13_7__section_ed1_nz1_wr [1] https://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_feature_differences.html ... View more

Minor correction POST meant to be PUT but I trust you've figured this out. ... View more

Hi AnandMS,   From what I can tell the pg_dump command expects pg_dump [connection-option...] [option...] [dbname] see https://www.postgresql.org/docs/9.1/static/app-pgdump.html   grep -oE 'db.(user|name)=.*' /etc/cloudera-scm-server/db.properties in my environment give me the followig output.   db.name=scm db.user=cloudera-scm   threfore db.user I set in -U cloudera-scm followed by scm.   effectively your command should look like   # pg_dump -h hostname -p 7432 -U cloudera-scm scm > /tmp/scm_server_db_backup.$(date +%Y%m%d)   ... View more

Within Cloudera Manage you could use the Custom Kerberos Keytab Retrieval Script, an example script is documented here http://www.cloudera.com/documentation/enterprise/latest/topics/sg_keytab_retrieval_script.html     ... View more

Of course [1]       [1] http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_create_local_package_repo.html ... View more

>  We were intially provided the below URLs to be placed under /etc/yum.repos.d under cloudera-manager.repo > ...  we in the bank cannot connect to outside URLs due to security issue You will need to contact the person who created your internal repo [1] to create a repo for Redhat/CentOS 7. Effectively your baseurl = .../redhat/7/...  <== point to Redhat/CentOS 7 packages internal url just an example (notice the 7) ==> baseurl=[base URL]     [1]  baseurl=[base url] ... View more