XMPP, Server does not use any supported authentication method

Paul Aurich darkrain42 at pidgin.im
Sun Sep 11 17:38:50 EDT 2011


And Alexander Ustinov spoke on 09/11/2011 01:14 PM, saying:
> 
>> Could you get a debug log of Pidgin starting up?  Disable all accounts, and
>> then quit Pidgin.  From the command line, run:
>>
>>     pidgin -d>  ~/pidgin.log
>>
>> After it starts up, go ahead and enable one of your XMPP accounts, and then
>> quit Pidgin, and attach that debug log.
>>
>> ~Paul
>>
> 
> 
> Here it goes.

Sigh, so Cyrus SASL is initializing properly.  It's just failing and has a
totally insufficient amount of logging.

In no particular order:
   * What are the contents of /etc/hosts and /etc/hostname?
   * Which exact version of Cyrus SASL is installed (`apt-cache policy
libsasl2-modules`)
   * If you upgrade to the Cyrus SASL from Debian Unstable, does it work?

It may come down to your needing to install the Cyrus SASL debug symbols
and start bisecting sasl_client_new() with breakpoints until we can figure
out what is actually returning SASL_FAIL (-1) (or adding breakpoints to
every SASL_FAIL return in Cyrus SASL and seeing which one hits).

> 
> Thanks,
> Alexander.
> 

~Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://pidgin.im/pipermail/support/attachments/20110911/87cde48d/attachment.pgp>


More information about the Support mailing list