Member since
07-08-2013
548
Posts
59
Kudos Received
53
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2560 | 08-17-2019 04:05 PM | |
2541 | 07-26-2019 12:18 AM | |
8789 | 07-17-2019 09:20 AM | |
4972 | 06-18-2018 03:38 AM | |
12410 | 04-06-2018 07:13 AM |
08-16-2017
06:52 AM
Quote: "...this issue is going to be fixed in later releases of 5.12 ?" Yes, the issue is already fixed and committed, we aim to have it available in the next 5.12.x maintenance release.
... View more
08-16-2017
05:47 AM
1 Kudo
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
08-14-2017
03:46 AM
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
08-11-2017
12:36 AM
1 Kudo
Hi awsbiddata, There are some examples that you might find interesting, they show you how to use the CM API here; a. to auto configure [0] OR b. manually assign [1a,b] Regards, Michalis [0] # we will auto-assign roles; you can manually assign roles using the # /clusters/{clusterName}/services/{serviceName}/role endpoint or by using # ApiService.createRole() cluster.auto_assign_roles() cluster.auto_configure() [1a] https://github.com/cloudera/cm_api/blob/master/python/examples/auto-deploy/deploycloudera.py#L267-L269 [1b] https://github.com/gdgt/cmapi
... View more
08-11-2017
12:21 AM
2 Kudos
Hi leiyz, You will need to umount /run/user/42/gvfs or /run/user/42 then you should be able to start the Cloudera Agent. You are indeed running into the same issue as josholsan in this case [0] [0] http://community.cloudera.com/t5/Cloudera-Manager-Installation/Cloudera-Manager-Agent-cannot-connect-with-supervisor-Failed-to/td-p/58522
... View more
08-10-2017
03:06 AM
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
08-09-2017
10:49 AM
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
08-09-2017
03:02 AM
1 Kudo
If running as sudo the results is giving you OSError: [Errno 13] Permission denied: '/run/user/112/gvfs' You will need to temporary unmount that tmpfs mount/path, which will allow the Cloudera Manager Agent to start - you are hitting a known issue which will be addressed in the future maintenance release. Regards, Michalis
... View more
08-08-2017
06:51 AM
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
06-16-2017
08:42 AM
Then you will need to parse the REST result of the /hosts?view=full [0] endpoint which gives you map of host-to-roleRef "The list of roles assigned to this host." $ curl -u admin:admin -X GET "http://cm-server:7180/api/v12/hosts?view=full" [0] https://cloudera.github.io/cm_api/apidocs/v16/ns0_apiHost.html
... View more