After Reboot of V2.3.1 Secure Oracle Big Data Appliance Cluster, Zookeeper/HDFS Service Status is BAD (Doc ID 1609811.1)

Last updated on OCTOBER 11, 2016

Applies to:

Big Data Appliance Integrated Software - Version 2.3.1 and later
Linux x86-64

Symptoms

Oracle Big Data Appliance (BDA) cluster has V2.3.1 installed with Kerberos enabled. Primary and secondary key distribution centers (KDC) reside on BDA nodes.

After Reboot of V2.3.1 Secure BDA Cluster, Zookeeper and other HDFS Service Status is BAD.

Zookeeper services are bad as they are exiting abnormally.

Noticed below error in Zookeeper logs

Unexpected exception, exiting abnormally
java.io.IOException: Could not configure server because SASL configuration did not allow the  ZooKeeper server to authenticate itself properly: javax.security.auth.login.LoginException: Receive timed out
   at org.apache.zookeeper.server.ServerCnxnFactory.configureSaslLogin(ServerCnxnFactory.java:205)
   at org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:87)
   at org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:135)
   at org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:116)
   at org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:79)
9:12:23.652 AM     ERROR     org.apache.zookeeper.server.quorum.QuorumPeerMain   

Trying to Re-generate/Generate Credentials thru Cloudera Manager fails with 'Communication failure with server while initializing kadmin interface'

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