[jadmin] Problems with Bandersnatch - Update from jabberd2 version 2.0-s11 to 2.1.2

[Irmãos Bocchi & Cia Ltda]

Good Morning!

Tonigth I have upgraded my jabberd2 from version 2.0-s11 to the new and 
revolutionary jabberd 2.1.2 (xiaoka's build). My bandersnatch in prior 
version works fine, but now the bandersnatch output this error when I 
try to run the daemon

[root at router]in /usr/local/etc/jabberd/bandersnatch-0.4.RC1
 >> # ./bandersnatch2.pl config.xml
    DBI::db=HASH(0x14b5be0) trace level set to 0x0/2 (DBI @ 0x0/0) in 
DBI 1.48-nothread (pid 1507)
SASL Negotiation Failed at 
/usr/lib/perl5/site_perl/5.8.7/POE/Component/Jabber/Client/J2.pm line 374.
Connected to MySQL database (bandersnatch at 127.0.0.1) ...Failed to 
authenticate
We got disconneted
!   -> DESTROY for DBD::mysql::db (DBI::db=HASH(0x14b5be0)~INNER)
&imp_dbh->mysql: 1471d68
!   <- DESTROY= undef during global destruction
[root at router]in /usr/local/etc/jabberd/bandersnatch-0.4.RC1
 >> #

This errors ocurrs with the bandersnatch version 0.0.3. With the version 
0.4, this is the message error
[root at router]in /usr/local/etc/jabberd/bandersnatch-0.4.RC1
 >> # ./bandersnatch config.xml
XML::Stream: new: hostname = (router)
XML::Stream: SetCallBacks: tag(node) func(CODE(0x12d56a0))
NJ::Component: SetCallBacks: tag(message) func(CODE(0x12d5910))
NJ::Component: SetCallBacks: tag(presence) func(CODE(0x12d58a0))
NJ::Component: SetCallBacks: tag(iq) func(CODE(0x12d57e0))
NJ::Component: SetCallBacks: tag(iq) func(CODE(0x12bdaa0))
NJ::Component: SetCallBacks: tag(receive) func(CODE(0x129eda0))
NJ::Component: SetCallBacks: tag(presence) func(CODE(0x12ad8d0))
NJ::Component: SetCallBacks: tag(message) func(CODE(0x12af640))
NJ::Component: Connect: type(accept)
NJ::Component: Connect: hostname(localhost) 
secret(newjabberkickingmyass) componentname(bandersnatch.someserver.com.br)
XML::Stream: Connect: type(tcpip)
XML::Stream: Connect: Got a connection
XML::Stream: Send: (<?xml version='1.0'?><stream:stream version='1.0' 
xmlns:stream='http://etherx.jabber.org/streams' 
xmlns='jabber:component:accept' to='bandersnatch.someserver.com.br' 
from='router' xml:lang='en' >)
XML::Stream: Read: buff(<?xml version='1.0'?><stream:stream 
xmlns:stream='http://etherx.jabber.org/streams' 
xmlns='jabber:component:accept' to='router' 
from='bandersnatch.someserver.com.br' version='1.0' 
id='86tcwv3ds7ef523cvuwkn0g71o948z2g5wt2sxfk'><stream:features 
xmlns:stream='http://etherx.jabber.org/streams'><mechanisms 
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism></mechanisms></stream:features>)
NJ::Component: Connect: connection made
NJ::Component: SendXML: 
sent(<handshake>ac68346f9ad01536458fb7a66c59cbac68fd349e</handshake>)
XML::Stream: Send: 
(<handshake>ac68346f9ad01536458fb7a66c59cbac68fd349e</handshake>)
XML::Stream: Read: buff(<stream:error 
xmlns:stream='http://etherx.jabber.org/streams'><not-authorized 
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text 
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>hash didn't match, auth 
failed</text></stream:error></stream:stream>)
NJ::Component: Process: status(-1)
NJ::Component: Process: return(-1)
[08:57:22] Bandersnatch: (ERROR) Unable to connect to Jabber server 
(localhost) ...
[08:57:22] Bandersnatch:         (Bad handshake.)
[root at router]in /usr/local/etc/jabberd/bandersnatch-0.4.RC1
 >> #


Remembering: the old configuration works FINE! I only upgrade the 
software and recreate the c2s.xml file to reflect the new features, 
using the new c2s.xml file as an example to upgrade the old file.

I read in this maillist about an upgrade to XML::Stream to use the new 
Authen::SASL features 
(http://marc.info/?l=jabber-jadmin&m=117214314726199&w=2), but I don't 
find any reference to find this patch. Anybody can help me??

Obs.: Xiaoka have a great work with this new version. I use for a long 
time the 2.0-s11 version. Excepting this little problem with this 
bandersnatch, I like soo much this work! Good Job!!!

Best regards


------------------------------------------------
Os e-mails enviados por este domínio são verificados
por sistemas antivírus e antispam, visando a proteção
dos usuários e dos equipamentos de nossa empresa, bem como
para proteger o conteúdo e o trabalho de outros que
por ventura venham receber e-mails deste domínio.

O Grupo Bocchi se reserva no direito de, a qualquer
momento, bloquear ou inutilizar conteúdo de e-mails
que venham a ser prejudiciais para o ambiente de trabalho.

Caso este e-mail não possua conteúdo que seja relevante
à sua atividade profissional, ou a do usuário que a enviou,
por favor, delete-o imediatamente.

O Grupo Bocchi não se responsabiliza por qualquer dano 
ou prejuízo que a utilização indevida deste e-mail
possa causar a você ou sua empresa.

Em caso de dúvidas, favor entrar em contato.
---------------------------------------------


Grupo Irmãos Bocchi & Cia Ltda

http://www.ibocchi.com.br