Failed to Authenticate the HBase User
Issue
Failed to authenticate the HBase user.
Symptom
Failed to authenticate the HBase user on the client. The following error information is displayed:
2019-05-13 10:53:09,975 ERROR [localhost-startStop-1] xxxConfig.LoginUtil: login failed with hbaseuser and /usr/local/linoseyc/hbase-tomcat/webapps/bigdata_hbase/WEB-INF/classes/user.keytab. 2019-05-13 10:53:09,975 ERROR [localhost-startStop-1] xxxConfig.LoginUtil: perhaps cause 1 is (wrong password) keytab file and user not match, you can kinit -k -t keytab user in client server to check. 2019-05-13 10:53:09,975 ERROR [localhost-startStop-1] xxxConfig.LoginUtil: perhaps cause 2 is (clock skew) time of local server and remote server not match, please check ntp to remote server. 2019-05-13 10:53:09,975 ERROR [localhost-startStop-1] xxxConfig.LoginUtil: perhaps cause 3 is (aes256 not support) aes256 not support by default jdk/jre, need copy local_policy.jar and US_export_policy.jar from remote server in path ${BIGDATA_HOME}/jdk/jre/lib/security.
Cause Analysis
The version of the JAR file in the JDK used by the user is different from that of the JAR file authenticated by MRS.
Procedure
- Log in to the Master1 node as user root.
- Run the following command to check the JAR file authenticated by MRS:
ll /opt/share/local_policy/local_policy.jar
ll /opt/Bigdata/jdk{version}/jre/lib/security/local_policy.jar
- Download the JAR package queried in step 2 to the local host.
- Copy the downloaded JAR package to the local JDK directory /opt/Bigdata/jdk/jre/lib/security.
- Run the cd /opt/client/HBase/hbase/bin command to go to the bin directory of HBase.
- Run the sh start-hbase.sh command to restart HBase.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot