我在vmware中运行mapr沙盒。如何从运行在windows上的eclipse连接到此vm中运行的hbase？我一直收到安全错误
微克clientcnxn:102 - zookeeper.disableautowatchreset为false 2015-11-17 10:54:34调试zookeepersaslclient:222 - jaas logincontext是：client\u simple 2015-11-17 10:54:34信息login:293 - 已成功登录。2015-11-17 10:54:34信息管理员aslclient:285 - 客户端将使用gssapi作为sasl机制。2015-11-17 10:54:34调试aslclient:287 - 创建sasl客户端：client=tpham104；服务=Zookeeper；servicehostname=192.168.17.132 2015-11-17 10:54:39信息clientcnxn:975 - 正在打开到服务器192.168.17.132/192.168.17.132:5181的套接字连接。将尝试使用登录上下文部分“客户端\u简单”进行sasl身份验证2015-11-17 10:54:39信息clientcnxn:852 - 按照192.168.17.132/192.168.17.132:5181建立插座连接，启动会议2015-11-17 10:54:39调试clientcnxn:892 - 会话建立请求发送于192.168.17.132/192.168.17.132:5181 2015-11-17 10:54:39 info clientcnxn:1235 - 在服务器192.168.17.132/192.168.17.132:5181上完成会话建立，sessionid=0x15114be8996001e，协商超时=40000 2015-11-17 10:54:39erwatcher:430 - hconnection-0x2a1dd8a40x0，quorum=192.168.17.132:5181，baseznode=/hbase-received-zookeeper-event，type=none，state=syncconnected，path=null 2015-11-17 10:54:39调试客户端cnxnsocketnio:184 - 延迟非启动包：clientpath:null serverpath：空finished:false header：：0,3 replyheader:：0,0,0请求：：“/hbase/hbaseid，f response:：直到sasl身份验证完成。2015-11-17 10:54:39调试客户端cnxnsocketnio:184 - 延迟非启动包：clientpath:null serverpath：空finished:false header：：0,3 replyheader:：0,0,0请求：：“/hbase/hbaseid，f response:：直到sasl身份验证完成。2015-11-17 10:54:39调试aslclient:417 - clientcnxn:sendsaslpacket：长度=0 2015-11-17 10:54:39aslclient:365 - saslclient.evaluatechallenge（len=0）2015-11-17 10:54:39调试erwatcher:507 - hconnection-0x2a1dd8a4-0x15114be8996001e connected 2015-11-17 10:54:39错误aslclient:384 - 错误：（java.security.privilegedactionexception:javax.security.sasl.saslexception:gss initiate failed[由gssexException引起：未提供有效凭据（机制级别：找不到任何kerberos tgt）]）在评估zookeeper仲裁成员收到的sasl令牌时发生。zookeeper客户端将进入验证失败状态。2015-11-17 10:54:39错误clientcnxn:1015 - zookeeper仲裁成员的sasl身份验证失败：javax.security.sasl.saslexception:错误：（java.security.privilegedactionexception:javax.security.sasl.saslexception:gss initiate失败[原因是gssexException:未提供有效凭据（机制级别：找不到任何kerberos）tgt）]）在评估zookeeper仲裁成员收到的sasl令牌时发生。zookeeper客户端将进入验证失败状态。2015-11-17 10:54:39调试erwatcher:430 - hconnection-0x2a1dd8a4-0x15114be8996001e，quorum=192.168.17.132:5181，baseznode=/hbase接收到zookeeper事件，type=none，state=authfailed，path=null 2015-11-17 10:55:06警告zkutil:483 - hconnection-0x2a1dd8a4-0x15114be8996001e，法定人数=192.168.17.132:5181，baseznode=/hbase无法在znode（/hbase/hbaseid）org.apache.zookeeper.keeperexception$authfailedexception:keeperrorcode=authfailed for/hbase/hbaseid at org.apache.zookeeper.keeperexception.create（keeperexception）。java:123)在org.apache.zookeeper.keeperexception.create（keeperexception。java:51)在org.apache.zookeeper.zookeeper.exists（zookeeper。java:1045)位于org.apache.hadoop.hbase.zookeeper.recoverablezookeeper.exists（recoverablezookeeper。java:221)在org.apache.hadoop.hbase.zookeeper.zkutil.checkexists（zkutil。java:480)在org.apache.hadoop.hbase.zookeeper.zkclusterid.readclusteridznode（zkclusterid。java:65)在org.apache.hadoop.hbase.client.zookeeperregistry.getclusterid（zookeeperregistry）。java:83)在org.apache.hadoop.hbase.client.hconnectionmanager$hconnectionimplementation.retrieveclusterid（hconnectionmanager。java:912)在org.apache.hadoop.hbase.client.hconnectionmanager$hconnectionimplementation。java:706)在sun.reflect.nativeconstructoraccessorimpl.newinstance0（本机方法）位于sun.reflect.nativeconstructoraccessorimpl.newinstance（nativeconstructoraccessorimpl）。java:57)在sun.reflect.delegatingconstructoraccessorimpl.newinstance（delegatingconstructoraccessorimpl。java:45)在java.lang.reflect.constructor.newinstance（constructor。java:526)在org.apache.hadoop.hbase.client.hconnectionmanager.createconnection（hconnectionmanager）。java:461)在org.apache.hadoop.hbase.client.hconnectionmanager.createconnection（hconnectionmanager。java:440)在org.apache.hadoop.hbase.client.hconnectionmanager.getconnection（hconnectionmanager。java:321)在org.apache.hadoop.hbase.client.htable。java:198) 在org.apache.hadoop.hbase.client.htable。java:175)在com.optum.pafgen.service.hbaservice.main（hbaservice。java:58)