Jabber2 服务器安装求助
那位高手可以帮忙看看,编译安装jabber2,使用mysql,启动正常,使用gaim1.5登陆的时候服务器debug如下:
C2S : Tue Jun 6 13:09:43 2006 [notice] ready for connections
C2S : sx (io.c:159) 6 ready for reading
C2S : Tue Jun 6 13:10:09 2006 [notice] [8] [211.157.227.42, port=3738] connect
C2S : sx (io.c:165) tag 6 event 2 data 0x80a7098
C2S : Tue Jun 6 13:09:46 2006 c2s.c:554 reading from 6
C2S : Tue Jun 6 13:09:46 2006 c2s.c:579 read 232 bytes
C2S : sx (io.c:181) passed 232 read bytes
C2S : sx (chain.c:93) calling io read chain
C2S : sx (io.c:205) decoded read data (232 bytes): <route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' to='c2s' from='linuxsea'><iq xmlns='jabber:client' type='get' to='c2s' from='linuxsea' id='6leh4taf'><query xmlns='http://jabber.org/protocol/disco#info'/></iq></route>
C2S : sx (io.c:70) completed nad: <route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='linuxsea' to='c2s'><iq xmlns='jabber:client' id='6leh4taf' from='linuxsea' to='c2s' type='get'><query xmlns='http://jabber.org/protocol/disco#info'/></iq></route>
C2S : sx (chain.c:119) calling nad read chain
C2S : sx (io.c:124) tag 6 event 6 data 0x80a7050
C2S : Tue Jun 6 13:09:46 2006 c2s.c:774 not a c2s packet, dropping
C2S : Tue Jun 6 13:10:09 2006 c2s.c:417 accept action on fd 8
C2S : sx (sx.c:55) allocated new sx for 8
C2S : sx (server.c:236) doing server init for sx 8
C2S : sx (server.c:251) waiting for stream header
C2S : sx (server.c:254) tag 8 event 0 data 0x0
C2S : Tue Jun 6 13:10:09 2006 c2s.c:33 want read
C2S : Tue Jun 6 13:10:09 2006 c2s.c:381 read action on fd 8
C2S : sx (io.c:159) 8 ready for reading
C2S : sx (io.c:165) tag 8 event 2 data 0x80a9960
C2S : Tue Jun 6 13:10:09 2006 c2s.c:43 reading from 8
C2S : Tue Jun 6 13:10:09 2006 c2s.c:97 read 22 bytes
C2S : sx (io.c:181) passed 22 read bytes
C2S : sx (chain.c:93) calling io read chain
C2S : sx (io.c:205) decoded read data (22 bytes): <?xml version='1.0' ?>
C2S : Tue Jun 6 13:10:09 2006 c2s.c:381 read action on fd 8
C2S : sx (io.c:159) 8 ready for reading
C2S : sx (io.c:165) tag 8 event 2 data 0x80a9d80
C2S : Tue Jun 6 13:10:09 2006 c2s.c:43 reading from 8
C2S : Tue Jun 6 13:10:09 2006 c2s.c:97 read 113 bytes
C2S : sx (io.c:181) passed 113 read bytes
C2S : sx (chain.c:93) calling io read chain
C2S : sx (io.c:205) decoded read data (113 bytes): <stream:stream to='linuxsea' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
C2S : sx (server.c:11 stream request: to linuxsea from (null) version 1.0
C2S : sx (server.c:133) 8 state change from 0 to 1
C2S : sx (server.c:151) stream id is tu3qs0g9brpnxdnq6leh4tafuvkcupvokyeczvma
C2S : sx (server.c:181) prepared stream response: <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='linuxsea' version='1.0' id='tu3qs0g9brpnxdnq6leh4tafuvkcupvokyeczvma'>
C2S : sx (io.c:221) tag 8 event 1 data 0x0
C2S : Tue Jun 6 13:10:09 2006 c2s.c:38 want write
C2S : Tue Jun 6 13:10:09 2006 c2s.c:395 write action on fd 8
C2S : sx (io.c:293) 8 ready for writing
C2S : sx (io.c:251) encoding 182 bytes for writing: <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='linuxsea' version='1.0' id='tu3qs0g9brpnxdnq6leh4tafuvkcupvokyeczvma'>
C2S : sx (chain.c:79) calling io write chain
C2S : sx (io.c:312) handing app 182 bytes to write
C2S : sx (io.c:313) tag 8 event 3 data 0x80a9d68
C2S : Tue Jun 6 13:10:09 2006 c2s.c:104 writing to 8
C2S : Tue Jun 6 13:10:09 2006 c2s.c:108 182 bytes written
C2S : sx (server.c:29) stream established
C2S : sx (server.c:39) 8 state change from 1 to 3
C2S : sx (server.c:40) tag 8 event 4 data 0x0
C2S : sx (server.c:45) building features nad
C2S : sx (sasl.c:97) offering sasl mechanisms
C2S : sx (sasl.c:107) offering mechanism: DIGEST-MD5
C2S : sx (sasl.c:107) offering mechanism: PLAIN
C2S : Tue Jun 6 13:10:09 2006 bind.c:35 not auth'd, not offering resource bind
C2S : sx (io.c:346) tag 8 event 0 data 0x0
C2S : Tue Jun 6 13:10:09 2006 c2s.c:33 want read
C2S : Tue Jun 6 13:10:09 2006 c2s.c:395 write action on fd 8
C2S : sx (io.c:293) 8 ready for writing
C2S : sx (io.c:251) encoding 210 bytes for writing: <stream:features xmlns:stream='http://etherx.jabber.org/streams'><mechanisms xmlns='urn:ietf:paramsml:nsmpp-sasl'><mechanism>DIGEST-MD5</mechanism><mechanism>LAIN</mechanism></mechanisms></stream:features>
C2S : sx (chain.c:79) calling io write chain
C2S : sx (io.c:312) handing app 210 bytes to write
C2S : sx (io.c:313) tag 8 event 3 data 0x80a9d68
C2S : Tue Jun 6 13:10:09 2006 c2s.c:104 writing to 8
C2S : Tue Jun 6 13:10:09 2006 c2s.c:108 210 bytes written
C2S : sx (io.c:346) tag 8 event 0 data 0x0
C2S : Tue Jun 6 13:10:09 2006 c2s.c:33 want read
C2S : Tue Jun 6 13:10:09 2006 c2s.c:381 read action on fd 8
C2S : sx (io.c:159) 8 ready for reading
C2S : sx (io.c:165) tag 8 event 2 data 0x80a9d68
C2S : Tue Jun 6 13:10:09 2006 c2s.c:43 reading from 8
C2S : Tue Jun 6 13:10:09 2006 c2s.c:97 read 71 bytes
C2S : sx (io.c:181) passed 71 read bytes
C2S : sx (chain.c:93) calling io read chain
C2S : sx (io.c:205) decoded read data (71 bytes): <auth xmlns='urn:ietf:paramsml:nsmpp-sasl' mechanism='DIGEST-MD5'/>
C2S : sx (io.c:70) completed nad: <auth xmlns='urn:ietf:paramsml:nsmpp-sasl' mechanism='DIGEST-MD5'/>
C2S : sx (chain.c:119) calling nad read chain
C2S : sx (sasl.c:21 auth request from client (mechanism=DIGEST-MD5)
C2S : Tue Jun 6 13:10:09 2006 scod.c:123 creating new scod
C2S : sx (sasl.c:236) sasl context initialised for 8
C2S : Tue Jun 6 13:10:09 2006 main.c:265 sx sasl callback: get realm: realm is 'linuxsea'
C2S : Tue Jun 6 13:10:09 2006 scod.c:255 server start
C2S : Tue Jun 6 13:10:09 2006 scod.c:151 looking for mech 'DIGEST-MD5'
C2S : Tue Jun 6 13:10:09 2006 mech_digest_md5.c:435 DIGEST-MD5 server start
C2S : Tue Jun 6 13:10:09 2006 mech_digest_md5.c:78 escaped 'linuxsea' into '"linuxsea"'
C2S : Tue Jun 6 13:10:09 2006 mech_digest_md5.c:261 generated nonce: d031d7ba5de3b219eca1899ab73beb28c5b0f6df
C2S : Tue Jun 6 13:10:09 2006 mech_digest_md5.c:78 escaped 'd031d7ba5de3b219eca1899ab73beb28c5b0f6df' into '"d031d7ba5de3b219eca1899ab73beb28c5b0f6df"'
C2S : Tue Jun 6 13:10:09 2006 mech_digest_md5.c:464 generated initial challenge: realm="linuxsea",nonce="d031d7ba5de3b219eca1899ab73beb28c5b0f6df",qop="auth",charset=utf-8,algorithm=md5-sess
C2S : sx (sasl.c:280) sasl handshake in progress (challenge: realm="linuxsea",nonce="d031d7ba5de3b219eca1899ab73beb28c5b0f6df",qop="auth",charset=utf-8,algorithm=md5-sess)
C2S : sx (chain.c:106) calling nad write chain
C2S : sx (io.c:369) queueing for write: <challenge xmlns='urn:ietf:paramsml:nsmpp-sasl'>cmVhbG09ImxpbnV4c2VhIixub25jZT0iZDAzMWQ3YmE1ZGUzYjIxOWVjYTE4OTlhYjczYmViMjhjNWIwZjZkZiIscW9wPSJhdXRoIixjaGFyc2V0PXV0Zi04LGFsZ29yaXRobT1tZDUtc2Vzcw==</challenge>
C2S : sx (io.c:221) tag 8 event 1 data 0x0
C2S : Tue Jun 6 13:10:09 2006 c2s.c:38 want write
C2S : Tue Jun 6 13:10:09 2006 c2s.c:395 write action on fd 8
C2S : sx (io.c:293) 8 ready for writing
C2S : sx (io.c:251) encoding 212 bytes for writing: <challenge xmlns='urn:ietf:paramsml:nsmpp-sasl'>cmVhbG09ImxpbnV4c2VhIixub25jZT0iZDAzMWQ3YmE1ZGUzYjIxOWVjYTE4OTlhYjczYmViMjhjNWIwZjZkZiIscW9wPSJhdXRoIixjaGFyc2V0PXV0Zi04LGFsZ29yaXRobT1tZDUtc2Vzcw==</challenge>
C2S : sx (chain.c:79) calling io write chain
C2S : sx (io.c:312) handing app 212 bytes to write
C2S : sx (io.c:313) tag 8 event 3 data 0x80ab4d8
C2S : Tue Jun 6 13:10:09 2006 c2s.c:104 writing to 8
C2S : Tue Jun 6 13:10:09 2006 c2s.c:108 212 bytes written
C2S : sx (io.c:346) tag 8 event 0 data 0x0
C2S : Tue Jun 6 13:10:09 2006 c2s.c:33 want read
C2S : Tue Jun 6 13:10:09 2006 c2s.c:381 read action on fd 8
C2S : sx (io.c:159) 8 ready for reading
C2S : sx (io.c:165) tag 8 event 2 data 0x80a9e60
C2S : Tue Jun 6 13:10:09 2006 c2s.c:43 reading from 8
C2S : Tue Jun 6 13:10:09 2006 c2s.c:97 read 358 bytes
C2S : sx (io.c:181) passed 358 read bytes
C2S : sx (chain.c:93) calling io read chain
C2S : sx (io.c:205) decoded read data (358 bytes): <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>dXNlcm5hbWU9InRlc3QxIixyZWFsbT0ibGludXhzZWEiLG5vbmNlPSJkMDMxZDdiYTVkZTNiMjE5ZWNhMTg5OWFiNzNiZWIyOGM1YjBmNmRmIixjbm9uY2U9ImI1YTdiODg3MTE0OTU2NTg5MGQ3NWM3NzEyIixuYz0wMDAwMDAwMSxxb3A9YXV0aCxkaWdlc3QtdXJpPSJ4bXBwL2xpbnV4c2VhIixyZXNwb25zZT0wNTA1NTc1OTg2ODM1M2UxZGQ1NWQzNDgwYTMwMDY0YSxjaGFyc2V0PXV0Zi04</response>
C2S : sx (io.c:70) completed nad: <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>dXNlcm5hbWU9InRlc3QxIixyZWFsbT0ibGludXhzZWEiLG5vbmNlPSJkMDMxZDdiYTVkZTNiMjE5ZWNhMTg5OWFiNzNiZWIyOGM1YjBmNmRmIixjbm9uY2U9ImI1YTdiODg3MTE0OTU2NTg5MGQ3NWM3NzEyIixuYz0wMDAwMDAwMSxxb3A9YXV0aCxkaWdlc3QtdXJpPSJ4bXBwL2xpbnV4c2VhIixyZXNwb25zZT0wNTA1NTc1OTg2ODM1M2UxZGQ1NWQzNDgwYTMwMDY0YSxjaGFyc2V0PXV0Zi04</response>
C2S : sx (chain.c:119) calling nad read chain
C2S : sx (sasl.c:253) response from client
C2S : Tue Jun 6 13:10:09 2006 scod.c:299 server step
C2S : Tue Jun 6 13:10:09 2006 mech_digest_md5.c:481 DIGEST-MD5 server step; response: username="test1",realm="linuxsea",nonce="d031d7ba5de3b219eca1899ab73beb28c5b0f6df",cnonce="b5a7b8871149565890d75c7712",nc=00000001,qop=auth,digest-uri="xmpp/linuxsea",response=05055759868353e1dd55d3480a30064a,charset=utf-8
C2S : Tue Jun 6 13:10:10 2006 [notice] [8] SASL authentication succeeded: mechanism=DIGEST-MD5; authzid=test1@linuxsea
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:241 got key 'username' val 'test1'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:241 got key 'realm' val 'linuxsea'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:241 got key 'nonce' val 'd031d7ba5de3b219eca1899ab73beb28c5b0f6df'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:241 got key 'cnonce' val 'b5a7b8871149565890d75c7712'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:241 got key 'nc' val '00000001'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:241 got key 'qop' val 'auth'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:241 got key 'digest-uri' val 'xmpp/linuxsea'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:241 got key 'response' val '05055759868353e1dd55d3480a30064a'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:241 got key 'charset' val 'utf-8'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:498 extracting 'cnonce'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:498 extracting 'charset'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:498 extracting 'qop'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:498 extracting 'digest-uri'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:498 extracting 'realm'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:498 extracting 'nc'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:498 extracting 'response'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:498 extracting 'username'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:498 extracting 'nonce'
C2S : Tue Jun 6 13:10:10 2006 main.c:272 sx sasl callback: get pass (authnid=test1, realm=linuxsea)
C2S : Tue Jun 6 13:10:10 2006 authreg_mysql.c:66 prepared sql: SELECT `password`,`hash`,`token`,`sequence` FROM `authreg` WHERE `username` = 'test1' AND `realm` = 'linuxsea'
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:586 HEX(H(A1)) = 9ac78146bd32ba20f706c79b0eadab73
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:595 HEX(H(A2)) = 86ab925ae0b61a7746ccb3f043974c89
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:611 our response is 05055759868353e1dd55d3480a30064a, theirs is 05055759868353e1dd55d3480a30064a
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:623 matched, they're authenticated
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:650 HEX(H(rspauth A2)) = a474595a4bfdf7d9d9c81a650bfb2282
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:666 rspauth: d9f643ef82fed888bab5eaa5a3d9fe44
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:672 generated final challenge: rspauth=d9f643ef82fed888bab5eaa5a3d9fe44
C2S : sx (sasl.c:280) sasl handshake in progress (challenge: rspauth=d9f643ef82fed888bab5eaa5a3d9fe44)
C2S : sx (chain.c:106) calling nad write chain
C2S : sx (io.c:369) queueing for write: <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cnNwYXV0aD1kOWY2NDNlZjgyZmVkODg4YmFiNWVhYTVhM2Q5ZmU0NA==</challenge>
C2S : sx (io.c:221) tag 8 event 1 data 0x0
C2S : Tue Jun 6 13:10:10 2006 c2s.c:38 want write
C2S : Tue Jun 6 13:10:10 2006 c2s.c:395 write action on fd 8
C2S : sx (io.c:293) 8 ready for writing
C2S : sx (io.c:251) encoding 120 bytes for writing: <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cnNwYXV0aD1kOWY2NDNlZjgyZmVkODg4YmFiNWVhYTVhM2Q5ZmU0NA==</challenge>
C2S : sx (chain.c:79) calling io write chain
C2S : sx (io.c:312) handing app 120 bytes to write
C2S : sx (io.c:313) tag 8 event 3 data 0x80ab628
C2S : Tue Jun 6 13:10:10 2006 c2s.c:104 writing to 8
C2S : Tue Jun 6 13:10:10 2006 c2s.c:108 120 bytes written
C2S : sx (io.c:346) tag 8 event 0 data 0x0
C2S : Tue Jun 6 13:10:10 2006 c2s.c:33 want read
C2S : Tue Jun 6 13:10:10 2006 c2s.c:381 read action on fd 8
C2S : sx (io.c:159) 8 ready for reading
C2S : sx (io.c:165) tag 8 event 2 data 0x80ab628
C2S : Tue Jun 6 13:10:10 2006 c2s.c:43 reading from 8
C2S : Tue Jun 6 13:10:10 2006 c2s.c:97 read 53 bytes
C2S : sx (io.c:181) passed 53 read bytes
C2S : sx (chain.c:93) calling io read chain
C2S : sx (io.c:205) decoded read data (53 bytes): <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl' />
C2S : sx (io.c:70) completed nad: <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'/>
C2S : sx (chain.c:119) calling nad read chain
C2S : sx (sasl.c:253) response from client
C2S : Tue Jun 6 13:10:10 2006 scod.c:299 server step
C2S : Tue Jun 6 13:10:10 2006 mech_digest_md5.c:481 DIGEST-MD5 server step; response:
ROUT: Tue Jun 6 13:10:11 2006 [notice] [127.0.0.1, port=54695] disconnect
ROUT: sx (io.c:392) tag 10 event 1 data 0x0
ERROR: sm died. Shutting down server.
JBRD: Got a signal... pass it on.
JBRD: It was a TERM. Shut it all down!
[jabber@sip-server bin]$
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论