Member since
10-04-2021
3
Posts
0
Kudos Received
0
Solutions
10-13-2021
05:25 AM
For the information, file credentialbuilder*.jar is not missing. The problem is this variable, RANGER_OZONE_PLUGIN_INSTALL_LIB, is pointing to wrong directory, /opt/cloudera/parcels/CDH-7.1.6-1.cdh7.1.6.p0.10506313:GPLEXTRAS-7.1.6-1.gplextras7.1.6.p0.10506313/lib/ranger-ozone-plugin/install/lib The correct directory is /opt/cloudera/parcels/CDH-7.1.6-1.cdh7.1.6.p0.10506313/lib/ranger-ozone-plugin/install/lib Before installing the parcel, this variable is pointing to the correct directory. I don't know why after GPL Extras parcel being installed, Cloudera Manager insert some string (:GPLEXTRAS-7.1.6-1.gplextras7.1.6.p0.10506313) in the variable. I think if I could edit it from Cloudera Manager, it should resolve the issues. Any advice how to edit this variable using Cloudera Manager?
... View more
10-12-2021
06:39 AM
I just install GPLExtras parcel in my cluster. After activate the parcel, the cluster need to be restart, so it could recognize the new parcel. But when the cluster restart, ozone manager is failed to start with error message: + RANGER_OZONE_PLUGIN_INSTALL_LIB=/opt/cloudera/parcels/CDH-7.1.6-1.cdh7.1.6.p0.10506313:GPLEXTRAS-7.1.6-1.gplextras7.1.6.p0.10506313/lib/ranger-ozone-plugin/install/lib
+ set +x
Error: Could not find or load main class org.apache.ranger.credentialapi.buildks Somehow, the RANGER_OZONE_PLUGIN_INSTALL_LIB variable referred to misdefined directory. I also found in file /var/run/cloudera-scm-agent/process/${OZONE_MANAGER process dir}, the PARCEL_DIRNAMES variable also misdefined similar to RANGER_OZONE_PLUGIN_INSTALL_LIB PARCEL_DIRNAMES='CDH-7.1.6-1.cdh7.1.6.p0.10506313:GPLEXTRAS-7.1.6-1.gplextras7.1.6.p0.10506313 How can I resolve these issues, because I could not found these variables in Cloudera Manager. Thank you for the advice.
... View more
Labels:
- Labels:
-
Cloudera Manager
10-05-2021
07:25 AM
We have a development cluster consists of CDP 7.1.6 with Nifi 1.13.2. The enviromment is Kerberised and use Ranger for the security, and connected to the AD server through sssd service. We already setup the Flows policies on the ranger, by defining user and group that exisiting in the ranger. When we try to access the Nifi UI, for user which define on Users of Flows policies, it works properly. But when login using user that define on the Groups of Flows policies, it gives error message: “INFO [NiFi Web Server-225822] o.a.n.w.a.c.AccessDeniedExceptionMapper identity[18330301], groups[] does not have permission to access the requested resource. Unable to view the user interface. Returning Forbidden response.” Nifi could not identified this user group. Could you please give advice how to resolve this issues, so Nifi could give access to this user, which define in the Groups of Flow policies. Thank you in advance for you help.
... View more
Labels:
- Labels:
-
Apache NiFi
-
Apache Ranger