国产一级a片免费看高清,亚洲熟女中文字幕在线视频,黄三级高清在线播放,免费黄色视频在线看

打開APP
userphoto
未登錄

開通VIP,暢享免費(fèi)電子書等14項超值服

開通VIP
gloox 鏈接openfire服務(wù)器問題解決辦法

【問題】

-------------------------------------------------------

這是我用gloox的example改的,登錄服務(wù)器的時候出現(xiàn)來以下問題:

log: level: 0, area: 8, connection encryption active
log: level: 0, area: 16384, <?xml version='1.0' ?><stream:stream to='192.168.148.128' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'  xml:lang='en' version='1.0'>
log: level: 0, area: 8192, <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='localhost.localdomain' id='9c802eca' xml:lang='en' version='1.0'/>
log: level: 0, area: 8192, <stream:features><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression xmlns='http://jabber.org/features/compress'><method>zlib</method></compression><auth xmlns='http://jabber.org/features/iq-auth'/><register xmlns='http://jabber.org/features/iq-register'/></stream:features>
log: level: 0, area: 16384, <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/>
log: level: 0, area: 8192, <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cmVhbG09ImxvY2FsaG9zdC5sb2NhbGRvbWFpbiIsbm9uY2U9InZDakdkQldGckFoWXE3T3RJRDAxOHcwSmxra2F2RU4xM1VIS2V4RHIiLHFvcD0iYXV0aCIsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=</challenge>
log: level: 0, area: 4, processing SASL challenge
log: level: 0, area: 16384, <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>dXNlcm5hbWU9Inpob3UiLHJlYWxtPSJsb2NhbGhvc3QubG9jYWxkb21haW4iLG5vbmNlPSJ2Q2pHZEJXRnJBaFlxN090SUQwMTh3MEpsa2thdkVOMTNVSEtleERyIixjbm9uY2U9IjZiOGI0NTY3MzI3YjIzYzY2NDNjOTg2OTY2MzM0ODczIixuYz0wMDAwMDAwMSxxb3A9YXV0aCxkaWdlc3QtdXJpPSJ4bXBwLzE5Mi4xNjguMTQ4LjEyOCIscmVzcG9uc2U9MWFlZDU0MTFjZmMyYmQ2ZTcyZWM2M2NjNWQ0MjZjMzQsY2hhcnNldD11dGYtOA==</response>
log: level: 0, area: 8192, <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/></failure>
log: level: 2, area: 4, SASL authentication failed!
log: level: 0, area: 16384, </stream:stream>
message_test: disconnected: Device or resource busy
auth failed. reason: 6
SASL authentication failed!這個我問題我通過j->setForceNonSasl(true);來解決,不過還是有點(diǎn)問題,沒有解決其根本問題.

編譯結(jié)果如下:

[root@localhost jni]# g++ -g e2ee_client.cpp /usr/local/lib/libgloox.so -lpthread
e2ee_client.cpp: 在成員函數(shù)‘void MessageTest::start()’中:
e2ee_client.cpp:44:30: 警告:不建議使用‘void gloox::Client::setForceNonSasl(bool)’(聲明于 /usr/local/include/gloox/client.h:223)
運(yùn)行結(jié)果如下:

log: level: 0, area: 16384, </stream:stream>
message_test: disconnected: Device or resource busy
auth failed. reason: 0
這個錯誤沒有來,但是Device or resource busy這個問題還是不知道那里出問題來,希望有高手解答一下!


【解決辦法】

-------------------------------------------------------

今天心情不錯,終于解決了鏈接服務(wù)器失敗的原因。

SASL authentication failed 和Device or resource busy這兩個問題整整困惑了我很長很長時間 今天終于解決了。

其實這兩個問題的原因就是在于服務(wù)器認(rèn)證失敗的原因,我用Empathy鏈接服務(wù)器的時候會出現(xiàn)證書不一致的問題,它是可以處理證書不一致的問題的。我的服務(wù)器名為localhost.domin,而認(rèn)證的時候用的只是它的IP地址。從而導(dǎo)致證書不一致。

從而修改服務(wù)器名就能解決這個問題:

Openfire更服務(wù)器名稱的方法:
1.登陸openfire管理頁面,在主頁面下方選擇編輯屬性,修改服務(wù)器名稱為當(dāng)前主機(jī)名稱,點(diǎn)擊保存屬性,按頁面提示重啟服務(wù)器。
2. 重啟后,主頁的服務(wù)器屬性下的服務(wù)器名稱出現(xiàn)一個嘆號,鼠標(biāo)放上去顯示Found RSA certificate that is not valid for the server domain, 這樣是由于RSA認(rèn)證無效造成的,需要對新的服務(wù)器進(jìn)行RSA證書的配置。
3.選擇【服務(wù)器設(shè)置】菜單,選擇左下方的【服務(wù)器證書】,會看到兩個證書,點(diǎn)擊后面的刪除按鈕全部刪除。刪除后按系統(tǒng)提示重啟服務(wù)器。
4.重啟后,系統(tǒng)提示“一個或更多的證書丟失。單擊這里產(chǎn)生自定義簽名證書”。點(diǎn)擊后,自動生成和新的服務(wù)器匹配的RSA證書。生成后,按系統(tǒng)提示重啟。
5.重啟后,再次登錄,會看到主界面的服務(wù)器名稱的嘆號消失了,openfire正常,客戶端可以正常登陸了。

修改后運(yùn)行程序如下:

log: level: 0, area: 8, This is gloox 0.9.9.12, connecting...
log: level: 1, area: 32, notice: no SRV record found for 192.168.148.128, using default port.
log: level: 0, area: 32, connecting to 192.168.148.128 (192.168.148.128:5222)
log: level: 0, area: 16384, <?xml version='1.0' ?><stream:stream to='192.168.148.128' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'  xml:lang='en' version='1.0'>
log: level: 0, area: 8192, <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='192.168.148.128' id='d1314c34' xml:lang='en' version='1.0'/>
log: level: 0, area: 8192, <stream:features><starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression xmlns='http://jabber.org/features/compress'><method>zlib</method></compression><auth xmlns='http://jabber.org/features/iq-auth'/><register xmlns='http://jabber.org/features/iq-register'/></stream:features>
log: level: 0, area: 16384, <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
log: level: 0, area: 8192, <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
log: level: 0, area: 4, starting TLS handshake...
status: 3
issuer: CN=192.168.148.128
peer: CN=192.168.148.128
protocol: TLS1.0
mac: SHA1
cipher: AES-128-CBC
compression: NULL
log: level: 0, area: 8, connection encryption active
log: level: 0, area: 16384, <?xml version='1.0' ?><stream:stream to='192.168.148.128' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'  xml:lang='en' version='1.0'>
log: level: 0, area: 8192, <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='192.168.148.128' id='d1314c34' xml:lang='en' version='1.0'/>
log: level: 0, area: 8192, <stream:features><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression xmlns='http://jabber.org/features/compress'><method>zlib</method></compression><auth xmlns='http://jabber.org/features/iq-auth'/><register xmlns='http://jabber.org/features/iq-register'/></stream:features>
log: level: 0, area: 16384, <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/>
log: level: 0, area: 8192, <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cmVhbG09IjE5Mi4xNjguMTQ4LjEyOCIsbm9uY2U9IjhINnJoN2NPcytGcWFEdVVKaFJJYkRDQWRxSElvNldFZTY0MVpZYWwiLHFvcD0iYXV0aCIsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=</challenge>
log: level: 0, area: 4, processing SASL challenge
log: level: 0, area: 16384, <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>dXNlcm5hbWU9InVzZXIiLHJlYWxtPSIxOTIuMTY4LjE0OC4xMjgiLG5vbmNlPSI4SDZyaDdjT3MrRnFhRHVVSmhSSWJEQ0FkcUhJbzZXRWU2NDFaWWFsIixjbm9uY2U9IjZiOGI0NTY3MzI3YjIzYzY2NDNjOTg2OTY2MzM0ODczIixuYz0wMDAwMDAwMSxxb3A9YXV0aCxkaWdlc3QtdXJpPSJ4bXBwLzE5Mi4xNjguMTQ4LjEyOCIscmVzcG9uc2U9OTc1Njc1MTllNmNlN2Y3YTRlMjhjNTBmMWY1ZTEwZWMsY2hhcnNldD11dGYtOA==</response>
log: level: 0, area: 8192, <success xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cnNwYXV0aD00OWEzZGE0YWUwNWNmY2I3NWJiZTdjYjMxNGMxOGMxOA==</success>
log: level: 0, area: 4, SASL authentication successful
log: level: 0, area: 16384, <?xml version='1.0' ?><stream:stream to='192.168.148.128' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'  xml:lang='en' version='1.0'>
log: level: 0, area: 8192, <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='192.168.148.128' id='d1314c34' xml:lang='en' version='1.0'/>
log: level: 0, area: 8192, <stream:features><compression xmlns='http://jabber.org/features/compress'><method>zlib</method></compression><bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'/><session xmlns='urn:ietf:params:xml:ns:xmpp-session'/></stream:features>
log: level: 0, area: 16384, <iq type='set' id='bind'><bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'/></iq>
log: level: 0, area: 8192, <iq type='result' id='bind' to='192.168.148.128/d1314c34'><bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'><jid>user@192.168.148.128/d1314c34</jid></bind></iq>
log: level: 0, area: 16384, <iq type='set' id='session'><session xmlns='urn:ietf:params:xml:ns:xmpp-session'/></iq>
log: level: 0, area: 8192, <iq type='result' id='session' to='user@192.168.148.128/d1314c34'><session xmlns='urn:ietf:params:xml:ns:xmpp-session'/></iq>
log: level: 0, area: 16384, <presence><priority>0</priority></presence>
log: level: 0, area: 16384, <iq type='get' id='uid1'><query xmlns='jabber:iq:register'/></iq>
log: level: 0, area: 8192, <iq type='result' id='uid1' to='user@192.168.148.128/d1314c34'><query xmlns='jabber:iq:register'><username>user</username><password/><email/><name/><x xmlns='jabber:x:data' type='form'><title>XMPP Client Registration</title><instructions>Please provide the following information</instructions><field var='FORM_TYPE' type='hidden'><value>jabber:iq:register</value></field><field var='username' type='text-single' label='Username'><required/><value>user</value></field><field var='name' type='text-single' label='Full name'><value/></field><field var='email' type='text-single' label='Email'><value/></field><field var='password' type='text-private' label='Password'><required/></field></x><registered/></query></iq>
the account already exists.
鏈接服務(wù)器成功,這破玩意真實讓人淡疼!


(###)

本站僅提供存儲服務(wù),所有內(nèi)容均由用戶發(fā)布,如發(fā)現(xiàn)有害或侵權(quán)內(nèi)容,請點(diǎn)擊舉報。
打開APP,閱讀全文并永久保存 查看更多類似文章
猜你喜歡
類似文章
XMPP-TLS和SASL握手 | 姜糖水
ejabberd分析(四) 用戶登錄
RFC3920可擴(kuò)展消息出席協(xié)議(XMPP):核心
Openfire與XMPP協(xié)議
XMPP RFC閱讀筆記
H3C NETCONF簡介
更多類似文章 >>
生活服務(wù)
分享 收藏 導(dǎo)長圖 關(guān)注 下載文章
綁定賬號成功
后續(xù)可登錄賬號暢享VIP特權(quán)!
如果VIP功能使用有故障,
可點(diǎn)擊這里聯(lián)系客服!

聯(lián)系客服