On BDA 4.9 "bdacli enable sentry" Fails with "ERROR: Ran kinit oracle and it returned code(1) instead of 0" (Doc ID 2425615.1)

Last updated on NOVEMBER 08, 2022

Applies to:

Symptoms

When trying to enable Sentry on a BDA 4.9 cluster via the "bdacli enable sentry", it fails with error like:

# bdacli enable sentry
<clustername-node1>.domain.realm
<clustername-node2>.domain.realm
<clustername-node3>.domain.realm
<clustername-node4>.domain.realm
<clustername-node5>.domain.realm
<clustername-node6>.domain.realm
...
INFO: Logging all actions in /opt/oracle/BDAMammoth/bdaconfig/tmp/<clustername-nodeX>-20180716055726.log and traces in /opt/oracle/BDAMammoth/bdaconfig/tmp/<clustername-nodeX>-20180716055726.trc
INFO: This is the install of the primary rack
INFO: Creating nodelist files...
...
INFO: Setting up Sentry admin role
kadmin: Incorrect password while initializing kadmin interface
kadmin: Incorrect password while initializing kadmin interface
kadmin: Incorrect password while initializing kadmin interface
kadmin: Incorrect password while initializing kadmin interface

ERROR: Ran kinit oracle and it returned code(1) instead of 0 and output is
kinit: Client not found in Kerberos database while getting initial credentials

INFO: Running bdadiagcluster...
INFO: Please get the Big Data Appliance cluster diagnostic bundle at /tmp/bdadiagcluster_1531719693.zip
Exiting...

 If the command "bdacli getinfo cluster_sentry_enabled" is subsequently run, it returns false, but Cloudera Manager (CM) shows Sentry status is healthy (green when viewed in CM).

Changes

 Ran bdacli command to enable Sentry on BDA cluster.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.