BDD : Failed to start Studio with exit code 233.

(Doc ID 2245583.1)

Last updated on MARCH 18, 2017

Applies to:

Oracle Big Data Discovery - Version 1.3.2.0.0 and later
Information in this document applies to any platform.

Symptoms

BDA 4.6 with Cloudera 5.8.2, BDD 1.3.2

After Enabling the Kerberos on top of BDA, there are problems on initial start of BDD. When running "bdd-admin start", it is just hanging after showing running for some components, but it is hanging after "Starting Dgraph Gateway ..Success".


Steps to reproduce

---------------------
1. Copy bdd.keytab to <BDD_HOME>/common/kerberos/bdd.keytab.

2. *Rerun* bdd-admin.sh to ensure all Kerberos related configurations are
set. The following is the command:
./bdd-admin.sh publish-config kerberos on -k -t -p

Both , and should be the absolute path. Since
there is a bdd-admin script bug in BDD 1.2, the *must* be use
<BDD_HOME>/common/kerberos/bdd.keytab as a workaround.

3. After Kerberos is enabled, please do the following check:
3.1. Check the existence of <BDD_HOME>/common/kerberos/bdd.keytab on both BDD
nodes and Hadoop nodes.
3.2. Check ${WEBLOGIC_DOMAIN_NAME}/config/studio/portal-ext.properties on
Admin Server. The value of krb5.principal should be bdd@BDAU1.EXELONDS.COM.
The value of krb5.keytab should be <BDD_HOME>/common/kerberos/bdd.keytab
3.3. Check <BDD_HOME>/dataprocessing/edp_cli/config/edp.properties on Admin
Server. The values of localKerberosPrincipal and clusterKerberosPrincipal
should be bdd@BDAU1.EXELONDS.COM. The value of localKerberosKeytabPath and
clusterKerberosKeytabPath should be <BDD_HOME>/common/kerberos/bdd.keytab.

4. Restart all components of BDD.
./bdd-admin.sh restart




Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms