Member since
05-27-2014
1499
Posts
77
Kudos Received
44
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3176 | 05-04-2020 11:56 AM | |
1953 | 05-01-2020 10:43 AM | |
2076 | 04-28-2020 03:11 PM | |
3554 | 04-28-2020 10:35 AM | |
2449 | 04-13-2020 10:44 AM |
05-10-2019
10:00 AM
Hi @Ryanp , You are very welcome and glad to hear the issue is resolved! Thanks, Li
... View more
05-09-2019
01:44 PM
2 Kudos
Hi @Ryanp , Here are the snippet from the knowledge article: A workaround can be achieved using the steps below. (NMS=Navigator Metadata Server) 1. Identify IP address of the NMS. (can be gathered in Cloudera Management services->instances->Navigator Metadata Server) 2. Add the following line to the bottom of /etc/hosts on the NMS 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 <NMS_IP_ADDRESS> java.sun.com 3. On NMS, install httpd, depending on your Linux distribution. As this host does not have internet access, you will need to manually import and install rpms. https://httpd.apache.org/docs/2.4/platform/rpm.html 4. Make a directory for java dtd file, and adjust permissions. mkdir /var/www/html/dtd; chown 755 /var/www/html/dtd 5. Acquire Java DTD file from the following URL. http://java.sun.com/dtd/web-app_2_3.dtd 6. Copy the file to /var/www/html/dtd directory on the NMS. Ensure the file is readable by "other". 7. Enable httpd server sudo systemctl enable httpd; sudo systemctl start httpd 8. Start NMS. NOTE: httpd must run for each NMS restart, this is not a one-off workaround. Systemctl command should ensure that this is the case. If the above workaround is not possible, a patch is also available from Cloudera Support until this is resolved in an upcoming release of Cloudera Manager. Thanks and hope this helps, Li
... View more
05-09-2019
10:31 AM
1 Kudo
Hi @michalr , Here is the documentation you can follow on how to install NiFi: https://docs.hortonworks.com/HDPDocuments/CFM/CFM-1.0.0/installation/content/overview.html Thanks, Li
... View more
05-09-2019
10:11 AM
1 Kudo
Hi @Ryanp , Does your cluster happen to be isolated from Internet? If so, then you may hit a known issue: In Cloudera Manager 6.2.0, if the Navigator Metadata server host doesn't have access to the internet, the Metadata data server role will fail to start. We have a knowledge article on this topic and it outlines the workaround steps to fix the issue: https://community.cloudera.com/t5/Customer/Navigator-Metadata-Server-Doesn-t-start-on-isolated-cluster/ta-p/89479 Thanks, Li
... View more
04-30-2019
09:41 AM
Hi @gunjan , There is a new feature added in Hue latest version which it moves the source file to create table to a .scratchdir to handle moving file easily. However, if the create table fails, then there are files in .scratchdir left behind and future create tables fails. We have opened an internal jira to handle this in a better way. Could you please remove the .scratchdir and try again as a workaround? Thanks, Li
... View more
04-23-2019
01:44 PM
Hi @gunjan , Could you please share the versions of Hue you are using? Are you using upstream version or the vesion comes with CDH? Thanks, Li
... View more
03-25-2019
11:10 AM
Hi @MantuDeka , Yes, if event server is not working, you won't be able to receive alerts. The alerts basically are the events which are marked as alerts based on CM configuration checking. About Report Manager, we need to check the RM process logs and role log for more details about what went wrong. By default: 1) On the Report Manager host, find out the process logs: /var/run/cloudera-scm-agent/process/<process-ID>-cloudera-mgmt-REPORTSMANAGER/logs/stderr and stdout.log 2) On the same host, find out the role log: /var/log/cloudera-scm-headlamp/mgmt-cmf-mgmt-REPORTSMANAGER-<hostname>.log.out Thanks and hope it helps, Li
... View more
03-20-2019
06:35 PM
3 Kudos
Hi @MantuDeka , Thanks for providing the log file. The error message indicates that the Event Server index has an corruption. However, the log snippet does not tell what caused it. For resolution, there is an option to attempt to fix the index which involves some steps, however the index may not be recoverable. Alternatively a quick fix would be to start the Event Server with a fresh new index. This will not cause any impact to cluster operation, but you will not be able to search for previous events in Cloudera Manager UI, CM -> Diagnostics -> Events page. Here are the steps for quick fix: 1. Stop the Event Server role instance in CM 2. Backup the current data directory (you can find the value from CM UI and search for -> "Event Server Index Directory"), default value usually is /var/lib/cloudera-scm-eventserver/ (just for safety reasons, this backup is likely not needed afterwards) 3. Empty the data directory: # rm -rf /var/lib/cloudera-scm-eventserver/* 4. Start the Event Server role instance in CM 5. Monitor the Event Server role logs in /var/log/cloudera-scm-eventserver/ directory, it should confirm the process is able to start up and operate Thanks, Li
... View more
03-19-2019
03:42 PM
1 Kudo
Hi @MantuDeka , To second @gzigldrum 's feedback, you can find out more information from some logs. By default: 1) On the Event Server host, find out the process logs: /var/run/cloudera-scm-agent/process/<process-ID>-cloudera-mgmt-EVENTSERVER/logs/stderr and stdout.log 2) On the same host, find out the role log: /var/log/cloudera-scm-eventserver/mgmt-cmf-mgmt-EVENTSERVER-<hostname>.log.out Thanks and hope it helps, Li
... View more
03-11-2019
10:41 AM
Hi @krieger , You are very welcome and glad to hear the issue got resolved! Cheers, Li
... View more