Installing BDD 1.2.2 on a BDA V4.5 AD Kerberos Enabled Cluster Fails with Permission Errors on bdd_create_hdfs_dirs (Doc ID 2158827.1)

Last updated on JULY 07, 2016

Applies to:

Big Data Appliance Integrated Software - Version 4.5.0 to 4.5.0 [Release 4.5]
Linux x86-64

Symptoms

Enabling BDD 1.2.2 on a BDA V4.5 AD Kerberos enabled cluster may fail when running the bdd_create_hdfs_dirs script. Permissions errors are raised.

1. "bdacli enable bdd" raises:

Error [64840]: (//bdanode05.example.com//Stage[main]/Bdd::Get_error_logs/File[bdd_geterrorlogs_script]/content) content changed '{md5}0bb05d726eefa03d5778b03eddab7ccf' to '{md5}1fd932d10d3ae69d3775371d921801e3'
Error [64840]: (//bdanode05.example.com//Stage[main]/Bdd::Get_error_logs/Exec[bdd_geterrorlogs]/returns) executed successfully
Error [64840]: (//bdanode05.example.com//Stage[main]/Bdd::Get_error_logs/Exec[bdd_geterrorlogs]/returns) executed successfully

But this error is a side effect of another puppet error and since BDD is not installed, some logs cannot be retrieved.

2. The file, bdd_create_hdfs_dirs_1467118281.out, in the Node 5 BDD error logs shows that the real problem is that bdd_create_hdfs_dirs script is failing. Output looks like:

java.io.IOException: Failed on local exception: java.io.IOException: javax.security.sasl.SaslException:
GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)];
Host Details : local host is: "bdanode05.example.com.tr/*.*.*.5"; destination host is: "bdanode05.example.com":8020;
at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:772)
at org.apache.hadoop.ipc.Client.call(Client.java:1475)
at org.apache.hadoop.ipc.Client.call(Client.java:1408)
at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:230)
at com.sun.proxy.$Proxy9.getFileInfo(Unknown Source)
at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getFileInfo(ClientNamenodeProtocolTranslatorPB.java:757)
...
Caused by: java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
at org.apache.hadoop.ipc.Client$Connection$1.run(Client.java:687)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1693)
at org.apache.hadoop.ipc.Client$Connection.handleSaslConnectionFailure(Client.java:650)
at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:738)
at org.apache.hadoop.ipc.Client$Connection.access$2900(Client.java:375)
at org.apache.hadoop.ipc.Client.getConnection(Client.java:1524)
at org.apache.hadoop.ipc.Client.call(Client.java:1447)
... 29 more
Caused by: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
at com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:211)
at org.apache.hadoop.security.SaslRpcClient.saslConnect(SaslRpcClient.java:413)
at org.apache.hadoop.ipc.Client$Connection.setupSaslConnection(Client.java:560)

 

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