这只兔子看起来烤熟了

你看的这篇文章是老的。

新的在这里：https://www.orchome.com/553



看下我的操作笔记

https://www.orchome.com/500

kdc的日志如下

Nov 28 20:46:18 devhost33-2 krb5kdc25748: AS_REQ (5 etypes {17 16 23 1 3}) 10.100.1.138: ISSUE: authtime 1511873178, etypes {rep=17 tkt=17 ses=17}, hadoop/devhost33-2@BSFIT for krbtgt/BSFIT@BSFIT

Nov 28 20:46:18 devhost33-2 krb5kdc25748: TGS_REQ (6 etypes {18 17 16 23 1 3}) 10.100.1.138: LOOKING_UP_SERVER: authtime 0,  hadoop/devhost33-2@BSFIT for zookeeper/10.100.1.138@BSFIT, Server not found in Kerberos database

你好，这边在启动kafka的时候报了如下一个错误，部署步骤是按照你这个文章一步步走的
[2017-11-28 20:46:18,929] ERROR An error: (java.security.PrivilegedActionException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7) - LOOKING_UP_SERVER)]) occurred when evaluating Zookeeper Quorum Member's  received SASL token. Zookeeper Client will go to AUTH_FAILED state. (org.apache.zookeeper.client.ZooKeeperSaslClient)
[2017-11-28 20:46:18,929] ERROR SASL authentication with Zookeeper Quorum member failed: javax.security.sasl.SaslException: An error: (java.security.PrivilegedActionException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7) - LOOKING_UP_SERVER)]) occurred when evaluating Zookeeper Quorum Member's  received SASL token. Zookeeper Client will go to AUTH_FAILED state. (org.apache.zookeeper.ClientCnxn)
[2017-11-28 20:46:18,929] INFO zookeeper state changed (AuthFailed) (org.I0Itec.zkclient.ZkClient)
[2017-11-28 20:46:18,929] INFO Terminate ZkClient event thread. (org.I0Itec.zkclient.ZkEventThread)
[2017-11-28 20:46:18,931] FATAL Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)