大数据：hue配置hive碰到的问题
No databases are available. Permissions could be
Could not start SASL: Error in sasl_client_start
(-4) SASL(-4): no mechanism available: No worthy mechs
Your query has the following
Could not start SASL: Error in sasl_client_start (-4) SASL(-4):
no mechanism available: No worthy mechs found
解决方法：
I am guessing you are missing the plain kerb
plugin. Try doing a:
install cyrus-sasl-plain
What auth are you using on HS2?
说明手册中要求装：
很明显还需要安装上面的库。
以上网友发言只代表其个人观点，不代表新浪网的观点或立场。& 相关文章 &
HBase 启动错误，HBase管理zookeeper ，无法定位登录配置
17:42:22,025 INFO org.apache.zookeeper.ClientCnxn: Opening socket connection to server xxxxx:2222. Will not attempt to authenticate using SASL (无法定位登录配置) 分析： 是由于zookeeper连接的问题，我用的是HBase管理的zookeeper，查找不到什么原因 解决： 改用zookeeper独立启动，不让
Zookeeper报错Will not attempt to authenticate using SASL解决办法
Zookeeper报错Will not attempt to authenticate using SASL解决办法
15:21:44 首先需要说的是，这个问题出现的原因很多，报的错误与实际可能相差比较远。总结如下： 一、调用端和服务器端版本不统一造成的！ 二、这个问题的出现，会伴随一个非常奇怪的现象。在master所在的pc上启动start-all时，内容提示所有的regionserver已经全部启动。但是，如果你去查看masterIP：60010时 会发现其他
ZooKeeper客户端 和服务器连接时版本问题
:43,008-[TS] INFO main-SendThread(17.22.17.1:2181) org.apache.zookeeper.ClientCnxn - Opening socket connection to server /17.22.17.1:2181. Will not attempt to authenticate using SASL (unknown error)
10:51:43,009-[TS] INFO main-SendThread
of this process is 27079@slave9
16:58:48,825 INFO org.apache.zookeeper.ClientCnxn: Opening socket connection to server 127.0.0.1/127.0.0.1:2181. Will not attempt to authenticate using SASL (Unable to locate a login configuration)
hbase windowns 下, Will not attempt to authenticate using SASL (无法定位登录配置)
- The identifier of this process is 9308@qin-PC
INFO ClientCnxn:966 - Opening socket connection to server namenode/192.168.120.129:2181. Will not attempt to authenticate using SASL (无法定位登录配置) 其实这个信息，并不是Hbase的异常，而是客户端找不到zookeeper的解析地址
，结果发现 stop-hbase.sh 后仍然存在 HregionServer，看说在关一次，就再关了一次，这回HMaster也粗线了 = = 3、查看 /data/hbase/logs 地下的hbase日志，发现这个错误： “zookeeper.ClientCnxn: Opening socket connecion to server localhost.localdomain/127.0.0.1:2181. Will not attempt to authenticate using SASL
solrcloud，tomcat，外部zookeeper配置详解
[main-SendThread(localhost:2181):ClientCnxn$SendThread@966] - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (无法定位登录配置)
JLine support is enabled
15:00:25,649 [myid:] - INFO
ZooKeeper Distributed模式
$MyWatcher@
Welcome to ZooKeeper!
22:03:15,888 [myid:] - INFO
[main-SendThread(192.168.130.62:2181):ClientCnxn$SendThread@966] - Opening socket connection to server /192.168.130.62:2181. Will not attempt to authenticate using SASL
node198/10.2.0.198:2181. Will not attempt to authenticate using SASL (无法定位登录配置)[cpt-service]16:34:47,906 INFO ClientCnxn:849 - Socket connection established to node198/10.2.0.198:2181, initiating session[cpt-service]16:34:47,907 DEBUG ClientCnxn:889
exited loop!
17:36:12,396 INFO
[RS:0;G460:43511-SendThread(localhost:2181)] zookeeper.ClientCnxn: Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
ORA-12638: 身份证明检索失败 的解决办法 日 星期三 11:42 the NTS option makes the Oracle client attempt to use your current Windows domain credentials to authenticate you with the Oracle server. This could fail for a couple of reasons: - The Oracle server
ZooKeeper做独立服务器运行(上)
connection to server 127.0.0.1/127.0.0.1:2181. Will not attempt toauthenticate using SASL (unknown error)
JLine support is enabled
07:39:20,460 [myid:] - INFO [main-SendThread(127.0.0.1:2181):ClientCnxn$SendThread@852] - Socketconnection
ZooKeeper安装运行
(localhost.localdomain:2181):ClientCnxn$SendThread@966] - Opening socket connection to server localhost.localdomain/127.0.0.1:2181. Will not attempt to authenticate using SASL (无法定位登录配置)
14:36:22,601 [myid:] - INFO
[main-SendThread
socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (无法定位登录配置) 原因：hive中没有设置zk hbase 中提示：WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes
ZooKeeper伪分布式集群安装及使用
/192.168.1.201:2181. Will not attempt to authenticate using SASL (Unable to locate a login configuration)
05:25:39,345 [myid:] - INFO
[main-SendThread(192.168.1.201:2181):ClientCnxn$SendThread@849] - Socket connection established to 192.168.1.201
: The identifier of this process is 14511@znb
14/06/27 18:34:51 INFO zookeeper.ClientCnxn: Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
14/06/27 18:34:51 INFO zookeeper.ClientCnxn
09:29:39,466
WARN ThreadPoolAsynchronousRunner:281 - Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@31d47845 (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt().
Apr 24, :06 AM org.apache.catalina.realm.LockOutRealm authenticate
WARNING: An attempt was made to authenticate the locked user "tomcat" 解决方案：用ali连接池 c3p0本身有bug!!!
socket connection to server hbase1/10.68.237.105:2181. Will not attempt to authenticate using SASL (unknown error)
JLine support is enabled
14:49:53,197 [myid:] - INFO
[main-SendThread(hbase1:2181):ClientCnxn$SendThread@849] - Socket
zookeeper.ClientCnxn: Opening socket connection to server hadoop/192.168.1.107:2181. Will not attempt to authenticate using SASL (无法定位登录配置)
14/07/26 19:44:54 INFO zookeeper.RecoverableZooKeeper: The identifier of this process is 6120@hugengyong-PC
attempt to create delete event with null entity解决办法
attempt to create delete event with null entity 这样的一个问题也折腾了半天。 症状： 报错，但是可以成功删除。 解决办法： 删除之前，先判断要删除的对象是否为空。 Eg： if(Object
session.delete(Object);
& 2012 - 2016 &
&All Rights Reserved. &
/*爱悠闲图+*/
var cpro_id = "u1888441";java smack openfire初始化失败
最近在学习如何实用openfire来做一个消息推送服务器。学习smack的时候按照官方文档写了一个test。
但是启动的时候就报错。ExceptionInInitializerError。
官方文档上并没有找到解决方法。
以下是异常：
java.lang.ExceptionInInitializerError
at org.jivesoftware.smack.SmackConfiguration.getVersion(SmackConfiguration.java:96)
at org.jivesoftware.smack.AbstractXMPPConnection.&clinit&(AbstractXMPPConnection.java:97)
at AccountManagerTest.login(AccountManagerTest.java:20)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: java.lang.IllegalStateException: org.xmlpull.v1.XmlPullParserException: could not load any factory class (even small or full default implementation); nested exception is:&
org.kxml2.io.XmlReader
at org.jivesoftware.smack.SmackInitialization.&clinit&(SmackInitialization.java:119)
... 29 more
Caused by: org.xmlpull.v1.XmlPullParserException: could not load any factory class (even small or full default implementation); nested exception is:&
org.kxml2.io.XmlReader
at org.xmlpull.v1.XmlPullParserFactory.newInstance(XmlPullParserFactory.java:225)
at org.xmlpull.v1.XmlPullParserFactory.newInstance(XmlPullParserFactory.java:76)
at org.jivesoftware.smack.SmackInitialization.processConfigFile(SmackInitialization.java:153)
at org.jivesoftware.smack.SmackInitialization.processConfigFile(SmackInitialization.java:148)
at org.jivesoftware.smack.SmackInitialization.&clinit&(SmackInitialization.java:116)
... 29 more
以下是问题补充：
：希望各位大神指导，谢谢。
根据官方的例子写的测试通过
XMPPTCPConnectionConfiguration config = XMPPTCPConnectionConfiguration.builder()
&.setUsernameAndPassword(username, password)
& & & & & & & & & .setServiceName(serviceName)
& & & & & & & & & .setHost(host)
& & & & & & & & & .setPort(5222)
& & & & & & & & & .setDebuggerEnabled(true)
& & & & & & & & & .setSecurityMode(SecurityMode.disabled)
& & & & & & & & & .build();
AbstractXMPPConnection conn2 = new XMPPTCPConnection(username,password,"127.0.0.1");
& & & & AbstractXMPPConnection conn2 = new XMPPTCPConnection(config);
& & & & try {
SASLAuthentication.registerSASLMechanism(new SASLPlainMechanism());
& & & & & & conn2.connect();
conn2.login();
& & & & & & conn2.login(username, password,resource);13年的时候用smack-3.3.0 写过连接openfire的各种例子，登录，注册，会话，收发文件，还弄了sock5相关的一堆，然后我就不再做这个事情了。
随着smack和openfire的版本变更，smack现在的稳定版已经到4.1.6,又给了我一个需求，一个用户有两个密码，要求两个不一样的密码都能登录，恶心不？
做openfire的同事说可以通过关闭sasl机制，然后可以曲线救国的实现这种需求。
在3.3的时候，是有方法直接关闭的&setSASLAuthenticationEnabled(&false);
可看smack 的 change log 应该是4.0之后就都没有了。
有人说：XMPPTCPConnectionConfiguration.builder() 中&.setSecurityMode(SecurityMode.disabled) 它可以，我想说您不看api啊
Sets the TLS security mode used when making the connection.
于是在放下smack3年后，开始建了个java工程，看看怎么曲线救国啊
1 首先要有实现了xmlpull 的jar包 ,下的是&kxml2-2.3.0.jar，不然会说少类
&2 &下载jxmpp
&3 &XMPPTCPConnectionConfiguration config = XMPPTCPConnectionConfiguration
.builder().setServiceName(&192.168.8.41&)
这个servicename 一定要和openfire中配置的domainname一样，我一开始就不一样，报
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using DIGEST-MD5: not-authorized
&，然后去openfire服务器上看了一下打印
SaslException == DIGEST-MD5: digest response format violation. Mismatched URI: xmpp/192.168.8.41; expecting: xmpp/192.168.88.41
4 需要jar包&smack-java7-4.1.6.jar
不然会报下面的错误
org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 5000ms (~5s). Used filter: No filter used or filter was 'null'.
5 &选择sasl 使用的Mechanism
我使用&SASLAuthentication.registerSASLMechanism(new SASLPlainMechanism()); 设置了不起作用，不明白为什么，有空的话跑一边源代码看看。
后来用下面的方式勉强可以设定Mechanism了。
SASLAuthentication.blacklistSASLMechanism(&CRAM-MD5&);
& & & & SASLAuthentication.blacklistSASLMechanism(&DIGEST-MD5&);
& & & & SASLAuthentication.unBlacklistSASLMechanism(&PLAIN&);&
到此，就可以顺利上线了。
折腾了2个多小时，最终，我也没有能取消sasl，还是修改了openfire的源码，就算实现了需求吧。特别特别的没精神，真怀念以前啊！
&&相关文章推荐
* 以上用户言论只代表其个人观点，不代表CSDN网站的观点或立场
访问：20554次
排名：千里之外
原创：12篇
转载：13篇
(4)(1)(3)(1)(2)(1)(9)(1)(1)(1)(1)