Member since
05-27-2014
1499
Posts
77
Kudos Received
44
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 4170 | 05-04-2020 11:56 AM | |
| 2926 | 05-01-2020 10:43 AM | |
| 2922 | 04-28-2020 03:11 PM | |
| 4736 | 04-28-2020 10:35 AM | |
| 3862 | 04-13-2020 10:44 AM |
03-27-2020
03:31 PM
1 Kudo
Hi @GTA ,
Please follow this to check if you have installed Navigator or not.
Step 1, check if you have the short cut link named "Cloudera Navigator" from Cloudera Manager UI > Clusters.
Step 2, if not, then click "Cloudera Management Service"
Step 3: The screenshot shows you what it will look like if you installed Navigator.
Step 4: If you have not installed Navigator, then you need to install it. Here is the doc of how to do that:
https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cm_ag_mgmt_service.html#xd_583c10bfdbd326ba-3ca24a24-13d80143249--7f1a__section_pgy_ngy_jk
Hope this helps!
Li
... View more
03-26-2020
11:25 PM
1 Kudo
Hi @GTA ,
If your Cloudera Enterprise Trial has not ended yet, then the enterprise features should be there and that includes Navigator.
Could you please check if the trial license expired? If not, please provide some more information about the issue then. For example, what do you see when you try to access Navigator home page? What are the Navigator instances installed where you can find out from Cloudera Manager UI? Some screenshots may help out here. Also, if you see any error messages, it will help to share that error with log files (CM server log, Navigator metadata server log etc).
Thanks,
Li
... View more
03-26-2020
11:54 AM
Hi @syedshakir ,
Thanks for your update. Could you please clarify if you are talking about a new issue here? The original issue is not able to access oozie workflow from my documents and got 402 error message. And the latest update you mentioned about users not able to kill jobs.
If the original issue got resolved, please close this thread and I would suggest you opening a new thread to explain what is the new issue and give some error message and screenshots will help.
Thanks,
Li
... View more
03-26-2020
09:53 AM
1 Kudo
Hi @GTA ,
Cloudera Navigator requires a Cloudera Enterprise license. Please see this doc for details:
https://docs.cloudera.com/documentation/enterprise/6/6.2/topics/cm_ag_licenses.html#cmug_topic_13_7__section_b3q_pvz_qm
Check the license page from Cloudera Manger to make sure you have a Cloudera Enterprise license.
Thanks,
Li
... View more
03-24-2020
07:54 PM
Hi @Mondi ,
The source of this issue is the interpretation of the $SERVICENAMEPATTERN variable which is being translated to yarnPATTERN in your case. In the code, there is a bug where a variable $SERVICENAMEPATTERN is clashed with the another variable name $SERVICENAME hence causes the probem.
Yes, Cloudera Manager 6.3.3 does have the bug fix.
Hope this helps!
Li
... View more
03-24-2020
11:12 AM
1 Kudo
Hi @Mondi,
Could you please share your Cloudera Manager version? There was a known bug which can cause the error you are seeing. Cloudera Manager 5.15.x and later should have the fix.
Thanks and hope this helps,
Li
... View more
03-19-2020
03:18 PM
1 Kudo
Hi @cbfr ,
Thanks for reaching out. You are hitting a known bug which is fixed in CM 5.16.2. Can you upgrade to CM5.16.2? If not, you can use CM API to update the configuration in order to workaround this.
Thanks and hope this helps,
Li
... View more
02-21-2020
01:24 PM
Hi @syedshakir,
Can you please try steps below?
Login to Hue UI as an admin user
Go to: Manage Users -> Groups -> Select the group (xxxx) your user ID belongs to
The UI becomes Hue Groups - Edit group: xxxx.
Scroll down from the permission section.
As below screen shows, check the checkbox oozie.access
Thanks and hope this helps!
... View more
02-11-2020
03:14 PM
1 Kudo
Hi @TR7_BRYLE ,
What is your Ambari version? You may want to check this knowledge article:
https://my.cloudera.com/knowledge/ERROR-quot-Request-to-https-AMBARI-SERVER-8441-agent-v1?id=273271
In case you can not access above, here are some details:
Cause:
This issue occurs when ethernet card or the switch does not support Jumbo frame, but the Jumbo frame (MTUSIZE=9000) is set in the network configuration.
To verify if the Jumbo frame is enabled, check the content of network interface configuration by running the following:
cat /etc/sysconfig/network-scripts/ifcfg-eth#
The Jumbo frame is enabled, if the following content (in bold) is displayed:
TYPE=Ethernet
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=static
IPADDR=xxx.xxx.xxx.xxx
NETMASK=xxx.xxx.xxx.xxx
MTUSIZE=9000
Instructions: To resolve this issue, do the following for each node with the issue:
1. From /etc/sysconfig/network-scripts/ifcfg-eth#1, remove the following:
MTUSIZE=9000
2. Restart the network:
/etc/initd/network restart
3. Restart the ambari-agent:
ambari-agent restart
Thanks and hope this helps!
... View more
02-06-2020
08:03 AM
Hi @anis016 ,
Glad to hear the issue got resolved after downgrading OpenJDK version. I have seen some other customers who experienced the issues with u242 version.
Cheers!
... View more