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

Elias · ‎07-11-2022

Hi @Neera456 If the HDFS role (or any role, for that matter) is stuck in a STOPPING or STARTING state, this means that there could have been an interruption when the supervisor sent it's one time ACK. To solve this, you can use the following KB article: https://community.cloudera.com/t5/Customer/Role-Managed-by-Cloudera-Manager-Stuck-in-Stopping-or/ta-p/75181 If this does not work, we can edit the ROLES table. please let me know if this works

Elias · ‎06-08-2022

Do you mean BDR? If so: - do you have a license applied to the CM UI? - Are you logged in as an administrator?

Elias · ‎06-08-2022

Do you have SSH running on the host? Also check forward and reverse hostname lookup.

Elias · ‎06-08-2022

As of CMP7.5.1 we do support CM HA: https://docs.cloudera.com/cloudera-manager/7.5.1/managing-clusters/topics/cm-high-availability.html

Elias · ‎06-08-2022

You need. to use the paywall URL: https://archive.cloudera.com/p/cm6/6.3.0/redhat7/yum/RPMS/x86_64/ (notice the '/p'/ in the URL) You will need your credentials

Elias · ‎05-26-2022

Are all the hosts healthy? To check go to: CM -> hosts -> All hosts

Elias · ‎04-27-2022

The speed unknown is simply stating that the agent could not collect the data that would allow the speed to be tested. The agent status being Bad, most likely means that the agent may not be heart - beating in. When this happens, check the heartbeat from the Host page.

Elias · ‎01-18-2022

The data directory for the event server may be corrupt. You can try the following: 1. Make sure the Event server role is stopped. 2. Edit the current data directory (default is /var/lib/cloudera-scm-eventserver), by adding a -2' or 'old',etc. 3. Start the Event server. If it starts , then it is a good indicator that the data directory became corrupt.

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 · ‎07-09-2019

Thank you for alerting us to this issue. We have initiated an internal jira to have this corrected ASAP.

Elias · ‎11-16-2018

You can edit the baseurl in the /etc/yum.repos.d/cloudera-manager.repo file to point to 5.15.1 (latest as of today for c5).For example: FROM: baseurl=https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5/ TO: baseurl=https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.15.1/ Run: yum clean all Then the installation will work

Elias · ‎10-22-2018

Hi Nukala, The following is from the docuentation I referenced in my last update: " This new feature is supported with new properties and attributes displayed in the Cloudera Navigator console, to distinguish long-running from Altus clusters and to distinguish among transient clusters. For example, the Cluster Group property identifies all clusters that have been created using the same Altus Environment Name and Altus Cluster name. The Cluster Instance distinguishes each instance in the same group from the others, so that metadata and lineage extracted from transient clusters over time can be identified... " For Atlus Clusters, please se our Cloudera Enterprise in the Cloud documentation

Elias · ‎10-10-2018

Hi Nukala, Navigator can track multiple Cluster within the same Cloudera Manager instance. The "Cluster Group" is new feature that was developed to support Altus clusters. Please see our New Features and Changes in Cloudera Navigator Data Management documentation Elias

Elias · ‎09-26-2018

Hi Nukala, Thank you for the information. "... does Cloudera Navigator has multiple cluster support as well? " Yes. the following is from our "Cloudera Navigator Frequently Asked Questions" documentation[1]: "... It provides a unified view of clusters associated with a given Cloudera Manager instance and lets you customize metadata, trace lineage, view audit events, and so on. " [1] https://www.cloudera.com/documentation/enterprise/5-13-x/topics/cn_faqs.html#navigator_faq_2

Elias · ‎09-25-2018

Also, you can have Cloudera Manager manage multiple Clusters. See our Managing Clusters documentation for details.

Elias · ‎09-25-2018

Hi Nukala, Can you please provide the Navigator and or Cloudera Manager version you are using?

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	‎07-25-2022 05:03 PM

Date Registered	‎08-22-2014 01:06 PM
Last Visited	‎07-25-2022 05:03 PM
Total Messages Posted	51
Total Kudos Received	7

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: Cloudera Manager Issue

Re: Cannot find the backup menu on Cloudera Manage...

Re: Unable to add the new host to the existing clu...

Re: Cloudera Manager High Availability

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

Re: NodeManager fails to start

Re: URGENT - Constant "Network Interface Speed Unk...

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

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: Checksum mismatch Cloudera 6.2.0

Re: Cloudera repository configuration issue - met...

Re: Cloudera Navigator Cluster Instance and Group

Re: Cloudera Navigator Cluster Instance and Group

Re: Cloudera Navigator Cluster Instance and Group

Re: Cloudera Navigator Cluster Instance and Group

Re: Cloudera Navigator Cluster Instance and Group

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.