免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
› 论坛 › IT运维 › Hadoop和大数据技术 › hdfs启用KerBeros验证之后出现（GSS initiate failed)）
最近访问板块 发新帖
查看: 59619 | 回复: 2
打印 上一主题 下一主题

[其他] hdfs启用KerBeros验证之后出现（GSS initiate failed)） [复制链接]

youzhengchuan

论坛徽章:
0
跳转到指定楼层
1楼 [收藏(0)] [报告]
发表于 2016-12-20 11:04 |只看该作者 |倒序浏览
本帖最后由 youzhengchuan 于 2016-12-20 11:09 编辑

目前只在Hadoop集群上配置了KerBeros认证（namenode，DataNode，journalnode）配置文件如下：
core-site.xml
  1. <!-- hadoop security configure -->
  2.         <property>
  3.                 <name>hadoop.security.authentication</name>
  4.                 <value>kerberos</value>
  5.          </property>
  6.          <property>
  7.                 <name>hadoop.security.authorization</name>
  8.                 <value>true</value>
  9.          </property>
  10.          <property>
  11.                 <name>hadoop.rpc.protection</name>
  12.                 <value>authentication</value>
  13.          </property>
  14.          <!-- hadoop security configure end -->
复制代码



hdfs-site.xml
  1. <!-- hadoop for kerberos configure -->
  2.     <!-- Kerberos NN -->
  3.     <property>
  4.         <name>dfs.block.access.token.enable</name>
  5.         <value>true</value>
  6.     </property>
  7.     <property>
  8.         <name>dfs.namenode.keytab.file</name>
  9.         <value>/etc/hadoop/hdfs.keytab</value>
  10.     </property>
  11.     <property>
  12.         <name>dfs.namenode.kerberos.principal</name>
  13.         <value>hdfs/_HOST@MYZONE.COM</value>
  14.     </property>
  15.     <property>
  16.         <name>dfs.namenode.kerberos.internal.spnego.principal</name>
  17.         <value>hdfs/_HOST@MYZONE.COM</value>
  18.     </property>
  19.     <!--<property>
  20.         <name>dfs.namenode.kerberos.https.principal</name>
  21.         <value>hdfs/_HOST@MYZONE.COM</value>
  22.     </property>-->
  23.     <!-- Kerberos DN -->
  24.     <property>
  25.         <name>dfs.datanode.keytab.file</name>
  26.         <value>/etc/hadoop/hdfs.keytab</value>
  27.     </property>
  28.     <property>
  29.         <name>dfs.datanode.kerberos.principal</name>
  30.         <value>hdfs/_HOST@MYZONE.COM</value>
  31.     </property>
  32.     <!--<property>
  33.         <name>dfs.datanode.kerberos.https.principal</name>
  34.         <value>hdfs/_HOST@MYZONE.COM</value>
  35.     </property>
  36.     <property>
  37.         <name>dfs.datanode.data.dir.perm</name>
  38.         <value>700</value>
  39.     </property>-->
  40.     <property>
  41.         <name>dfs.datanode.address</name>
  42.         <value>0.0.0.0:61004</value>
  43.     </property>
  44.     <property>
  45.         <name>dfs.datanode.http.address</name>
  46.         <value>0.0.0.0:61006</value>
  47.     </property>
  48.     <property>
  49.         <name>dfs.https.port</name>
  50.         <value>50470</value>
  51.     </property>
  52.     <property>
  53.         <name>dfs.http.policy</name>
  54.         <value>HTTPS_ONLY</value>
  55.     </property>
  56.     <property>
  57.         <name>dfs.data.transfer.protection</name>
  58.         <value>integrity</value>
  59.     </property>
  60.     <property>
  61.         <name>dfs.web.authentication.kerberos.keytab</name>
  62.         <value>/etc/hadoop/hdfs.keytab</value>
  63.     </property>
  64.     <property>
  65.         <name>dfs.web.authentication.kerberos.principal</name>
  66.         <value>hdfs/_HOST@MYZONE.COM</value>
  67.     </property>
  68.     <!-- hadoop for kerberos configure end -->
  69.     <!-- hadoop for kerberos configure for journalnode -->
  70.     <property>
  71.         <name>dfs.journalnode.keytab.file</name>
  72.         <value>/etc/hadoop/hdfs.keytab</value>
  73.     </property>
  74.     <property>
  75.         <name>dfs.journalnode.kerberos.principal</name>
  76.         <value>hdfs/_HOST@MYZONE.COM</value>
  77.     </property>
  78.     <property>
  79.         <name>dfs.journalnode.kerberos.internal.spnego.principal</name>
  80.         <value>hdfs/_HOST@MYZONE.COM</value>
  81.     </property>
  82.     <!-- hadoop for kerberos configure for journalnode end-->
复制代码


mapred.xml
  1. <blockquote><?xml version="1.0"?>
复制代码
ssl-client.xml
  1. <property>
  2.   <name>ssl.client.truststore.location</name>
  3.   <value>/root/truststore</value>
  4.   <description>Truststore to be used by clients like distcp. Must be specified.</description>
  5. </property>

  7. <property>
  8.   <name>ssl.client.truststore.password</name>
  9.   <value>changeit</value>
  10.   <description>Optional. Default value is "".</description>
  11. </property>

  13. <property>
  14.   <name>ssl.client.truststore.type</name>
  15.   <value>jks</value>
  16.   <description>Optional. The keystore file format, default value is "jks".
  17.   </description>
  18. </property>

  20. <property>
  21.   <name>ssl.client.truststore.reload.interval</name>
  22.   <value>10000</value>
  23.   <description>Truststore reload check interval, in milliseconds. Default value is 10000 (10 seconds).</description>
  24. </property>

  26. <property>
  27.   <name>ssl.client.keystore.location</name>
  28.   <value>/root/keystore</value>
  29.   <description>Keystore to be used by clients like distcp. Must be specified.</description>
  30. </property>

  32. <property>
  33.   <name>ssl.client.keystore.password</name>
  34.   <value>changeit</value>
  35.   <description>Optional. Default value is "".</description>
  36. </property>

  38. <property>
  39.   <name>ssl.client.keystore.keypassword</name>
  40.   <value>changeit</value>
  41.   <description>Optional. Default value is "".</description>
  42. </property>

  44. <property>
  45.   <name>ssl.client.keystore.type</name>
  46.   <value>jks</value>
  47.   <description>Optional. The keystore file format, default value is "jks".
  48.   </description>
  49. </property>
复制代码


ssl-server.xml
  1. <property>
  2.   <name>ssl.server.truststore.location</name>
  3.   <value>/root/truststore</value>
  4.   <description>Truststore to be used by NN and DN. Must be specified.</description>
  5. </property>

  7. <property>
  8.   <name>ssl.server.truststore.password</name>
  9.   <value>changeit</value>
  10.   <description>Optional. Default value is "".</description>
  11. </property>

  13. <property>
  14.   <name>ssl.server.truststore.type</name>
  15.   <value>jks</value>
  16.   <description>Optional. The keystore file format, default value is "jks".
  17.   </description>
  18. </property>

  20. <property>
  21.   <name>ssl.server.truststore.reload.interval</name>
  22.   <value>10000</value>
  23.   <description>Truststore reload check interval, in milliseconds.
  24.   Default value is 10000 (10 seconds).
  25.   </description>
  26. </property>

  28. <property>
  29.   <name>ssl.server.keystore.location</name>
  30.   <value>/root/keystore</value>
  31.   <description>Keystore to be used by NN and DN. Must be specified.</description>
  32. </property>

  34. <property>
  35.   <name>ssl.server.keystore.password</name>
  36.   <value>changeit</value>
  37.   <description>Must be specified.</description>
  38. </property>

  40. <property>
  41.   <name>ssl.server.keystore.keypassword</name>
  42.   <value>changeit</value>
  43.   <description>Must be specified.
  44.   </description>
  45. </property>

  47. <property>
  48.   <name>ssl.server.keystore.type</name>
  49.   <value>jks</value>
  50.   <description>Optional. The keystore file format, default value is "jks".
  51.   </description>
  52. </property>
复制代码


keytab文件：
  1. <blockquote># klist -ket /etc/hadoop/hdfs.keytab
复制代码


通过start-dfs.sh启动hdfs集群之后，能看到namenode、zkfc、DataNode、journalnode，都已经正常启动。
问题：
1、在管理页面上看DataNode都是dead状态。
2、通过日志分析，namenode连接journalnode失败
  1. 2016-12-20 10:23:15,996 WARN org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager: Waited 19015 ms (timeout=20000 ms) for a response for selectInputStreams. No responses yet.
  2. 2016-12-20 10:23:16,982 WARN org.apache.hadoop.hdfs.server.namenode.FSEditLog: Unable to determine input streams from QJM to [10.11.97.23:8485, 10.11.97.24:8485, 10.11.97.25:8485]. Skippi
  3. ng.
  4. java.io.IOException: Timed out waiting 20000ms for a quorum of nodes to respond.
  5.         at org.apache.hadoop.hdfs.qjournal.client.AsyncLoggerSet.waitForWriteQuorum(AsyncLoggerSet.java:137)
  6.         at org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.selectInputStreams(QuorumJournalManager.java:471)
  7.         at org.apache.hadoop.hdfs.server.namenode.JournalSet.selectInputStreams(JournalSet.java:278)
  8.         at org.apache.hadoop.hdfs.server.namenode.FSEditLog.selectInputStreams(FSEditLog.java:1463)
  9.         at org.apache.hadoop.hdfs.server.namenode.FSEditLog.selectInputStreams(FSEditLog.java:1487)
  10.         at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:644)
  11.         at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:281)
  12.         at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:1022)
  13.         at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:741)
  14.         at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:538)
  15.         at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:597)
  16.         at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:764)
  17.         at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:748)
  18.         at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1441)
  19.         at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1507)
复制代码
3、通过journalnode日志，发现namenode认证失败
  1. 2016-12-20 10:23:05,425 WARN org.apache.hadoop.util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
  2. 2016-12-20 10:23:07,110 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.22:52383:null (GSS initiate failed)
  3. 2016-12-20 10:23:07,192 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:59799:null (GSS initiate failed)
  4. 2016-12-20 10:23:08,709 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.22:59076:null (GSS initiate failed)
  5. 2016-12-20 10:23:10,149 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:17869:null (GSS initiate failed)
  6. 2016-12-20 10:23:13,265 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.22:2416:null (GSS initiate failed)
  7. 2016-12-20 10:23:14,653 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:63330:null (GSS initiate failed)
  8. 2016-12-20 10:23:17,083 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.22:41827:null (GSS initiate failed)
  9. 2016-12-20 10:23:17,256 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:41136:null (GSS initiate failed)
  10. 2016-12-20 10:23:21,249 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:18681:null (GSS initiate failed)
  11. 2016-12-20 10:23:21,806 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.22:39155:null (GSS initiate failed)
  12. 2016-12-20 10:23:21,827 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:48970:null (GSS initiate failed)
  13. 2016-12-20 10:23:21,838 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:44755:null (GSS initiate failed)
  14. 2016-12-20 10:23:25,880 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:12379:null (GSS initiate failed)
复制代码
4、通过DataNode的日志分析，发现DataNode连接namenode超时
  1. <blockquote>2016-12-20 10:56:05,183 WARN org.apache.hadoop.ipc.Client: Couldn't setup connection for hdfs/oitunnel-data-5@MYZONE.COM to oitunnel-data-2/10.11.97.22:53310
复制代码
5、通过namenode日志分析，DataNode认证失败
  1. 2016-12-20 10:55:31,898 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.25:33131:null (GSS initiate failed)
  2. 2016-12-20 10:55:32,581 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.23:16775:null (GSS initiate failed)
  3. 2016-12-20 10:55:32,915 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.24:56752:null (GSS initiate failed)
  4. 2016-12-20 10:55:33,109 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:31381:null (GSS initiate failed)
  5. 2016-12-20 10:55:33,334 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.26:13542:null (GSS initiate failed)
  6. 2016-12-20 10:55:33,758 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.27:9355:null (GSS initiate failed)
  7. 2016-12-20 10:55:34,239 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.23:64310:null (GSS initiate failed)
  8. 2016-12-20 10:55:34,788 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.23:31716:null (GSS initiate failed)
  9. 2016-12-20 10:55:34,822 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.25:29585:null (GSS initiate failed)
  10. 2016-12-20 10:55:35,887 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.23:8182:null (GSS initiate failed)
  11. 2016-12-20 10:55:37,023 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.25:34919:null (GSS initiate failed)
  12. 2016-12-20 10:55:37,616 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.24:6497:null (GSS initiate failed)
  13. 2016-12-20 10:55:37,698 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:63277:null (GSS initiate failed)
  14. 2016-12-20 10:55:38,340 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.26:40629:null (GSS initiate failed)
  15. 2016-12-20 10:55:38,463 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.27:7985:null (GSS initiate failed)
  16. 2016-12-20 10:55:38,572 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.27:3231:null (GSS initiate failed)
  17. 2016-12-20 10:55:38,705 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:4416:null (GSS initiate failed)
  18. 2016-12-20 10:55:39,097 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.21:51185:null (GSS initiate failed)
  19. 2016-12-20 10:55:39,129 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.26:48846:null (GSS initiate failed)
  20. 2016-12-20 10:55:39,961 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.23:7155:null (GSS initiate failed)
  21. 2016-12-20 10:55:40,731 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.27:33864:null (GSS initiate failed)
  22. 2016-12-20 10:55:40,887 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.24:29617:null (GSS initiate failed)
  23. 2016-12-20 10:55:42,029 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for 10.11.97.25:19005:null (GSS initiate failed)
复制代码


但是在KerBeros服务器上，能看到认证请求
  1. <blockquote>Dec 20 10:23:21 oi-tunnel15 krb5kdc[140489](info): TGS_REQ (5 etypes {17 16 23 1 3}) 10.11.97.21: ISSUE: authtime 1482200590, etypes {rep=17 tkt=18 ses=17}, hdfs/oitunnel-data-1@MYZONE.COM for hdfs/oitunnel-data-1@MYZONE.COM
复制代码




failed
youzhengchuan

论坛徽章:
0
2楼 [报告]
发表于 2016-12-20 11:11 |只看该作者
不知道为什么，有部分内容显示好像有限制，在这里补充。
keytab文件：
# klist -ket /etc/hadoop/hdfs.keytab
Keytab name: FILE:/etc/hadoop/hdfs.keytab
KVNO Timestamp Principal
---- ----------------- --------------------------------------------------------
3 12/19/16 21:42:23 hdfs/oitunnel-data-1@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-1@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-1@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-1@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-1@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-1@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-2@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-2@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-2@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-2@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-2@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-2@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-3@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-3@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-3@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-3@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-3@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-3@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-4@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-4@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-4@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-4@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-4@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-4@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-5@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-5@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-5@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-5@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-5@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-5@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-6@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-6@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-6@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-6@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-6@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-6@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-7@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 hdfs/oitunnel-data-7@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-7@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 mapred/oitunnel-data-7@MYZONE.COM (aes128-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-7@MYZONE.COM (aes256-cts-hmac-sha1-96)
3 12/19/16 21:42:23 yarn/oitunnel-data-7@MYZONE.COM (aes128-cts-hmac-sha1-96)
4 12/19/16 21:42:23 zookeeper/oi-tunnel08@MYZONE.COM (aes256-cts-hmac-sha1-96)
4 12/19/16 21:42:23 zookeeper/oi-tunnel08@MYZONE.COM (aes128-cts-hmac-sha1-96)
4 12/19/16 21:42:23 zookeeper/oi-tunnel09@MYZONE.COM (aes256-cts-hmac-sha1-96)
4 12/19/16 21:42:23 zookeeper/oi-tunnel09@MYZONE.COM (aes128-cts-hmac-sha1-96)
4 12/19/16 21:42:23 zookeeper/oi-tunnel10@MYZONE.COM (aes256-cts-hmac-sha1-96)
4 12/19/16 21:42:23 zookeeper/oi-tunnel10@MYZONE.COM (aes128-cts-hmac-sha1-96)
实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？
heguangwu

论坛徽章:
15
2015七夕节徽章 日期:2015-08-21 11:06:172017金鸡报晓 日期:2017-01-10 15:19:56极客徽章 日期:2016-12-07 14:07:30shanzhi 日期:2016-06-17 17:59:3115-16赛季CBA联赛之四川 日期:2016-04-13 14:36:562016猴年福章徽章 日期:2016-02-18 15:30:34IT运维版块每日发帖之星 日期:2016-01-28 06:20:0015-16赛季CBA联赛之新疆 日期:2016-01-25 14:01:34IT运维版块每周发帖之星 日期:2016-01-07 23:04:26数据库技术版块每日发帖之星 日期:2016-01-03 06:20:00数据库技术版块每日发帖之星 日期:2015-12-01 06:20:00IT运维版块每日发帖之星 日期:2015-11-10 06:20:00
3楼 [报告]
发表于 2016-12-20 11:20 |只看该作者
这种情况可能的问题很多，首先检查一下hadoop主机时间是否同步，另外GSS initiate failed日志后面一般会跟上一个原因，如Caused by XXXX
实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？
返回列表 发新帖
高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号：11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们：huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP