About Elias

Elias · ‎01-14-2022

Does the "/run/cloudera-scm-agent/process/22986-cloudera-mgmt-EVENTSERVER" directory exist?

Elias · ‎01-29-2021

Please read the "Enable the Cluster Utilization Report" section of our "Cluster Utilization Report" documentation[1]. There you can find information on the user that we recommend creating. [1] https://docs.cloudera.com/cloudera-manager/7.2.6/monitoring-and-diagnostics/topics/cm-enable-cluster-utilization-report.html

Elias · ‎11-22-2019

Hi @iamfromsky , It does sound like it may be a connection issue. You can run host inspector to see if CM detects any issues: CM -> Hosts -> All Hosts -> Inspect All hosts button You can also run the Network Performance Inspector, which allows you to examine the network performance among hosts and clusters managed by an instance of Cloudera Manager.

Elias · ‎02-23-2018

Thank you for the information. This does not appear to be the same issue as initiated in this thread. However, the error is clear: "ERROR Error, CM server guid updated, expected 93c963d9-3566-4f25-847a-faffb020866b, received ba4e4402-6ab3-4cdc-a403-39415df12824" There is a 'cm_guid' file that is used by the Cloudera Manager (CM) server to know which host belong to it. It appears that this host may have been part of a different CM cluster or the database was recently changed. This keeps users from inadvertently pointing the agent ot another CM instance. In any case, the solution is to: 1. Archive/remove the /var/lib/cloudera-scm-agent/cm_guid file. 2. Restart the agent: sudo service cloudera-scm-agent restart 3. Run the Host inspector, from the Hosts page in CM and verisfy that all hosts are functioning. If other hosts fail, they too may be in this state.

Elias · ‎02-23-2018

If the installation of the agent package is not succeeding, you should not have an agent log. Can you please run the follwoing and post the resilts? rpm -qa 'cloudera-manager-*'

Elias · ‎02-23-2018

Can you please let us know the OS and version and the contents of your /cloudera-manager repo file? cat /etc/redhat-release cat /etc/yum.repos.d/cloudera-manager.repo Also, the full error if possible.

Elias · ‎02-09-2018

Correct the network issue. Or use the following workaround: Create a temporary local repository as per the following KB article: [1] Deploying a Custom Patch Parcel Using Cloudera Manager https://cloudera-portal.force.com/articles/KB_Article/Deploying-a-Custom-Patch-Parcel-Using-Cloudera-Manager

Elias · ‎06-12-2017

That is great news! thank you for the update. For your Oozie question: If you do not know the password, you create a new oozie database as per our docuemtnation (Mysql for example[1]). Then add the oozie service: From Cloudera Manager's home screen, click on the Cluster drop down and select "Add Service" and follow the wizard. [1] https://www.cloudera.com/documentation/enterprise/5-7-x/topics/cm_ig_mysql.html#id_ijy_cwt_g5

Elias · ‎06-12-2017

Duplicate hosts are usually caused when the /var/lib/cloudera-scm-agent/uuid file has been edited or removed. To fix this issue you can try the following example: Let’s say: HostA is the original/correct host with Roles on it. HostB is the new duplicate/incorrect host. From the Cloudera Manager UI navigate to the Host page (CM -> Hosts -> “All Hosts”) 1. Identify original UUID Click on HostA -> Under “Details” record the “Host ID”. This is the UUID. Let’s call it “HostA-UUID” (it usually is a long alpha numeric number). 2. login to the Host from command line and navigate to var/lib/cloudera-scm-agent/ 3. Stop the agent service cloudera-scm-agent stop 4. Make a backup of the existing uuid file. 5. Change the contents of the uuid file with the original uuid (i.e HostA-UUID from step 1) echo -n “HostA-UUID” > /var/lib/cloudera-scm-agent/uuid For example: In my local env my UUID/Host ID is f7b2231c-dbd0-47ff-bf09-7961080cc065: echo –n “f7b2231c-dbd0-47ff-bf09-7961080cc065” > /var/lib/cloudera-scm-agent/uuid 6. Make sure you have not introduced a carriage return by running cat on the uuif file: cat uuid (your command line prompt should be on the same line as the restored uuid. For example: [mytestenv] cat uuid f7b2231c-dbd0-47ff-bf09-7961080cc065[mytestenv] 7. Start the Agent: service cloudera-scm-agent 8. From the Host page in Cloudera manager, check box HostB (the bad duplicate host with no roles) -> select the “Actions for Selected” drop down -> Delete

Elias · ‎05-20-2016

We need more information on which step is failing. i am assuming that the agents are failing during the Cluster install wizard. If this is the case you will need to follow our requirements docs: "One of the following, configured during initial installation of Cloudera Manager: Direct access to root user using the root password. Direct access to root user using a SSH key file. Passwordless sudo access for a specific user. This is the same requirement as the installation of CDH components on individual hosts, which is a requirement of the UNIX system in general. You cannot use another system (such as PowerBroker) that provides root/sudo privileges." http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_permissions.html#xd_583c10bfdbd326ba--6eed2fb8-14349d04bee--7eb1

Online	Offline
Last Visited	‎06-20-2023 09:27 AM

Member Since	‎08-22-2014 01:06 PM
Last Visited	‎06-20-2023 09:27 AM
Posts	61
Kudos received	7

Cloudera Community

Re: Not able to find cloudera-manager-agent 6.3.0 ...

Re: Please help me, I found log files making full ...

Re: CM yarn usage aggregation does not work

Re: CM/CDH 5.14 mirror issue

Re: Duplicate hostname in Cloudera Manager 5.7.2

Re: Please help me, I found log files making full ...

Re: CM yarn usage aggregation does not work

Re: Cloudera Manager agent bad healthy

Re: CM/CDH 5.14 mirror issue

Re: CM/CDH 5.14 mirror issue

Re: CM/CDH 5.14 mirror issue

Re: CM/CDH 5.14 mirror issue

Re: Duplicate hostname in Cloudera Manager 5.7.2

Re: Duplicate hostname in Cloudera Manager 5.7.2

Re: Installation failed. Failed to authenticate.