Member since
10-01-2018
802
Posts
143
Kudos Received
130
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2331 | 04-15-2022 09:39 AM | |
1798 | 03-16-2022 06:22 AM | |
5259 | 03-02-2022 09:44 PM | |
2128 | 03-02-2022 08:40 PM | |
1331 | 01-05-2022 07:01 AM |
04-27-2020
01:26 AM
@ankesh_clo This seems an issue with Symlink as well looking at the stack trace. Try the below method once. 1. Stop the Agent. 2. Remove the broken symlinks from /etc/alternatives and corresponding conf files from /var/lib/alternatives. 3. Remove the parcels/files from: /opt/cloudera/parcels /opt/cloudera/parcels/.flood /opt/cloudera/parcel-cache4. 4. Start the agent. The agent will redistribute the parcel and fix the Alternatives.
... View more
04-21-2020
09:13 AM
1 Kudo
@RajeshBodolla The general steps which I used to follow for Reinstall KTS from scratch this below, might be you are missing something. 1. Stop the KMS service 2. Delete the KMS service from the Cloudera Manager UI 3. Then remove all the contents under "rm -rf /var/lib/kms-keytrustee/" Note - Make sure that the hidden directory is also removed '/var/lib/kms-keytrustee/keytrustee/.keytrustee' 4. Now sync the Active and passive KTS using the following steps: a. Stop the Key Trustee Server service (Key Trustee Server service > Actions > Stop). b. Run the following command on the Active Key Trustee Server: $ sudo rsync -zav --exclude .ssl /var/lib/keytrustee/.keytrustee root@keytrustee02.example.com:/var/lib/keytrustee/. Note - Replace keytrustee02.example.com with the hostname of the Passive Key Trustee Server. c. Run the following command on the Passive Key Trustee Server: $ sudo ktadmin init d. Start the Key Trustee Server service (Key Trustee Server service > Actions > Start). e. Enable synchronous replication (Key Trustee Server service > Actions > Setup Enable Synchronous Replication in HA mode). f. Restart the Key Trustee Server service (Key Trustee Server service > Actions > Restart). Once this is done, now recreate the KMS service using the steps in the following link https://www.cloudera.com/documentation/enterprise/latest/topics/key_trustee_kms_ha.html
... View more
04-21-2020
01:36 AM
@bhara Unfortunately we don't have any public document for this but for overview you can follow this thread. https://community.cloudera.com/t5/Support-Questions/Version-upgrade-from-HDP-2-6-to-CDP/m-p/270234/highlight/true#M207374
... View more
04-21-2020
01:29 AM
2 Kudos
@Cl0ck You can always use OLD database, this is not am issue. For disabling TLS for admin console from CLI you can use below method. 1. Determine Cloudera Manager Database cat /etc/cloudera-scm-server/db.properties 2. Make database backup Postgres Backup: ---------------- pg_dump scm > scm_db_.backup 3. Connect to database Postgres Connect: ------------------ psql -U scm -h localhost -p 7432 -d postgres Password for user scm: postgres=> \l postgres=> \c scm 4. Show TLS related rows select * from CONFIGS where attr like '%tls%'; 5. Update TLS for web_tls update CONFIGS set value = 'false' where attr = 'web_tls'; You can generate the key and password as well with same method you did previously. Else please for reference you can use this doc. https://docs.cloudera.com/documentation/enterprise/5-14-x/topics/how_to_configure_cm_tls.html
... View more
04-21-2020
01:19 AM
@ankesh_clo Can you check /var/lib/cloudera-scm-agent/ dir on the new host, Then delete the file response.avro if exists. After that go to CM > Hosts > All hosts > Click on the newly added host and match the HOST ID with /var/lib/cloudera-scm-agent/uuid file if this is not in sync then please modify the uuid file as per HOST ID and restart the agent.
... View more
03-26-2020
12:20 PM
1 Kudo
Cloudera Quickstart VMs, Cloudera in particular and Hadoop in general have moved on. We are in a transition period away from that version of the Cloudera Quickstart VM, as it was extremely outdated and nearing end of support. As you noted, the up-to-date product is Cloudera Data Platform, which you can download at that URL. If you really must have a VM-based distribution of Hadoop, I strongly recommend you migrate to the HDP Sandbox. Cheers, Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. View solution in original post
... View more
03-25-2020
05:07 AM
@dil4852 Yes, in CDH for many services History and Rollback option is available so for CDSW. Refer the screenshot. You can follow the below link for more details. https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cm_mc_revert_configs.html
... View more
03-20-2020
01:23 AM
1 Kudo
@mon Cloudera Enterprise 6 requires Python 2.6 or higher on RHEL 6 compatible operating systems, but requires Python 2.7 or higher on RHEL 7 compatible operating systems. Only Hue and Spark2 needed Python 2.7 and rest of all CDH component in C6 train needs Python less than Python3. You can use Python 3 but not for CDH services until or unless you are trying some custom operations/job which needs some other Python version.
... View more
03-18-2020
02:32 AM
Sure, don't forget to close this thread my accepting this as solution once you done. Cheers,
... View more
03-18-2020
02:21 AM
@ManjunathK Can you check the jars in the hadoop class /usr/hdp/3.1.0.0-78/hadoop-hdfs/ in the problematic node and see if there is any 0 bytes file. If yes, then copy all the jars from working node and started the services.
... View more