[jadmin] Client doesn't connect

Wed Aug 8 13:44:30 CDT 2007

Hello everybody,

I'm trying to install Jabberd2 version 2.1.12 without success. The 
problem is the following:

Jabber is basically configured, it's running and registering new users, 
but, when I open my Jabber client, and try to log in, the client doesn't 
show any message (Pandion says to verify th username and Gaim crashes). 
Debug shows only the following:

C2S : Wed Aug  8 08:10:41 2007 [notice] [8] [10.100.5.3, port=4019] connect
C2S : sx (io.c:473) 8 state change from 3 to 6
C2S : sx (io.c:474) tag 8 event 7 data 0x0
C2S : Wed Aug  8 07:47:59 2007 c2s.c:443 close action on fd 8
C2S : sx (sx.c:72) freeing sx for 8
C2S : sx (sasl_gsasl.c:597) cleaning up conn state
C2S : Wed Aug  8 08:10:41 2007 c2s.c:460 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 : Wed Aug  8 08:10:41 2007 c2s.c:33 want read
C2S : Wed Aug  8 08:10:41 2007 c2s.c:424 read action on fd 8
C2S : sx (io.c:169) 8 ready for reading
C2S : sx (io.c:175) tag 8 event 2 data 0x8bbe2c8
C2S : Wed Aug  8 08:10:41 2007 c2s.c:43 reading from 8
C2S : Wed Aug  8 08:10:41 2007 c2s.c:97 read 21 bytes
C2S : sx (io.c:191) passed 21 read bytes
C2S : sx (chain.c:93) calling io read chain
C2S : sx (io.c:215) decoded read data (21 bytes): <?xml version="1.0"?>
C2S : Wed Aug  8 08:10:41 2007 c2s.c:424 read action on fd 8
C2S : sx (io.c:169) 8 ready for reading
C2S : sx (io.c:175) tag 8 event 2 data 0x8bbe2e0
C2S : Wed Aug  8 08:10:41 2007 c2s.c:43 reading from 8
C2S : Wed Aug  8 08:10:41 2007 c2s.c:97 read 140 bytes
C2S : sx (io.c:191) passed 140 read bytes
C2S : sx (chain.c:93) calling io read chain
C2S : sx (io.c:215) decoded read data (140 bytes): <stream:stream 
to="msg.constel.com.br" xml:lang="pt-br" xmlns="jabber:client" 
xmlns:stream="http://etherx.jabber.org/streams" version="1.0">
C2S : sx (server.c:118) stream request: to msg.constel.com.br 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 
9x9x3jmwafo9zxh6scm48u6f8s3zumx3k71nroj1
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='msg.constel.com.br' version='1.0' 
id='9x9x3jmwafo9zxh6scm48u6f8s3zumx3k71nroj1'>
C2S : sx (io.c:231) tag 8 event 1 data 0x0
C2S : Wed Aug  8 08:10:41 2007 c2s.c:38 want write
C2S : Wed Aug  8 08:10:41 2007 c2s.c:438 write action on fd 8
C2S : sx (io.c:303) 8 ready for writing
C2S : sx (io.c:261) encoding 192 bytes for writing: <?xml 
version='1.0'?><stream:stream 
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' 
from='msg.constel.com.br' version='1.0' 
id='9x9x3jmwafo9zxh6scm48u6f8s3zumx3k71nroj1'>
C2S : sx (chain.c:79) calling io write chain
C2S : sx (io.c:324) handing app 192 bytes to write
C2S : sx (io.c:325) tag 8 event 3 data 0x8bbe2c8
C2S : Wed Aug  8 08:10:41 2007 c2s.c:135 writing to 8
C2S : Wed Aug  8 08:10:41 2007 c2s.c:139 192 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_gsasl.c:237) offering sasl mechanisms
C2S : sx (sasl_gsasl.c:608) in _sx_sasl_gsasl_callback, property: 5
C2S : sx (sasl_gsasl.c:257) offering mechanism: PLAIN
C2S : sx (sasl_gsasl.c:257) offering mechanism: DIGEST-MD5
C2S : Wed Aug  8 08:10:41 2007 bind.c:38 not auth'd, offering auth and 
register
C2S : sx (io.c:358) tag 8 event 0 data 0x0
C2S : Wed Aug  8 08:10:41 2007 c2s.c:33 want read
C2S : Wed Aug  8 08:10:41 2007 c2s.c:438 write action on fd 8
C2S : sx (io.c:303) 8 ready for writing
C2S : sx (io.c:261) encoding 318 bytes for writing: <stream:features 
xmlns:stream='http://etherx.jabber.org/streams'><mechanisms 
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism><mechanism>DIGEST-MD5</mechanism></mechanisms><auth 
xmlns='http://jabber.org/features/iq-auth'/><register 
xmlns='http://jabber.org/features/iq-register'/></stream:features>
C2S : sx (chain.c:79) calling io write chain
C2S : sx (io.c:324) handing app 318 bytes to write
C2S : sx (io.c:325) tag 8 event 3 data 0x8bbe2c8
C2S : Wed Aug  8 08:10:41 2007 c2s.c:135 writing to 8
C2S : Wed Aug  8 08:10:41 2007 c2s.c:139 318 bytes written
C2S : sx (io.c:358) tag 8 event 0 data 0x0
C2S : Wed Aug  8 08:10:41 2007 c2s.c:33 want read
C2S : Wed Aug  8 08:10:41 2007 c2s.c:424 read action on fd 8
C2S : Wed Aug  8 08:10:41 2007 [notice] [8] [10.100.5.3, port=4019] 
disconnect jid=unbound, packets: 0
C2S : sx (io.c:169) 8 ready for reading
C2S : sx (io.c:175) tag 8 event 2 data 0x8bbe2c8
C2S : Wed Aug  8 08:10:41 2007 c2s.c:43 reading from 8
C2S : Wed Aug  8 08:10:41 2007 c2s.c:97 read 71 bytes
C2S : sx (io.c:191) passed 71 read bytes
C2S : sx (chain.c:93) calling io read chain
C2S : sx (io.c:215) decoded read data (71 bytes): <auth 
xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="DIGEST-MD5"/>
C2S : sx (io.c:70) completed nad: <auth 
xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/>
C2S : sx (chain.c:119) calling nad read chain
C2S : sx (sasl_gsasl.c:290) auth request from client (mechanism=DIGEST-MD5)
C2S : Wed Aug  8 08:10:41 2007 main.c:320 sx sasl callback: get realm: 
realm is 'msg.constel.com.br'
C2S : sx (sasl_gsasl.c:331) sasl context initialised for 8
C2S : sx (sasl_gsasl.c:382) sasl handshake in progress (challenge: , 
realm="msg.constel.com.br", nonce="QCr2lbjmCgb0UIUx3/oG7g==", qop="auth, 
auth-int, ", , , charset=utf-8, algorithm=md5-sess, )
C2S : sx (chain.c:106) calling nad write chain
C2S : sx (io.c:381) queueing for write: <challenge 
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>LCByZWFsbT0ibXNnLmNvbnN0ZWwuY29tLmJyIiwgbm9uY2U9IlFDcjJsYmptQ2diMFVJVXgzL29HN2c9PSIsIHFvcD0iYXV0aCwgYXV0aC1pbnQsICIsICwgLCBjaGFyc2V0PXV0Zi04LCBhbGdvcml0aG09bWQ1LXNlc3MsIA==</challenge>
C2S : sx (io.c:231) tag 8 event 1 data 0x0
C2S : Wed Aug  8 08:10:41 2007 c2s.c:38 want write
C2S : Wed Aug  8 08:10:41 2007 c2s.c:438 write action on fd 8
C2S : sx (io.c:303) 8 ready for writing
C2S : sx (io.c:261) encoding 236 bytes for writing: <challenge 
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>LCByZWFsbT0ibXNnLmNvbnN0ZWwuY29tLmJyIiwgbm9uY2U9IlFDcjJsYmptQ2diMFVJVXgzL29HN2c9PSIsIHFvcD0iYXV0aCwgYXV0aC1pbnQsICIsICwgLCBjaGFyc2V0PXV0Zi04LCBhbGdvcml0aG09bWQ1LXNlc3MsIA==</challenge>
C2S : sx (chain.c:79) calling io write chain
C2S : sx (io.c:324) handing app 236 bytes to write
C2S : sx (io.c:325) tag 8 event 3 data 0x8bbf980
C2S : Wed Aug  8 08:10:41 2007 c2s.c:135 writing to 8
C2S : Wed Aug  8 08:10:41 2007 c2s.c:139 236 bytes written
C2S : sx (io.c:358) tag 8 event 0 data 0x0
C2S : Wed Aug  8 08:10:41 2007 c2s.c:33 want read
C2S : Wed Aug  8 08:10:41 2007 c2s.c:424 read action on fd 8

I don't know what is happening. Can someone help me please.

Thanks.

Leandro.