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

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

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

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

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