Arch Linux

lvc

Member

Registered: 2011-10-12

Posts: 3

Prosody Cyrus SASL mod error initializing

I have prosody set up to use cyrus-sasl to authenticate. This was working well, until a recent full system upgrade. Now, I can't log in to XMPP.

On startup, prosody gives me the following error:

modulemanager: Error initializing module 'auth_cyrus' on 'localhost': /usr/lib/prosody/../../bin/prosody:169: loop or previous error loading module 'util.sasl_cyrus'

And when attempting to log in with pidgin:

# journalctl -fu prosody --since=+0
-- Logs begin at Thu 2012-12-06 04:27:09 EST. --
Sep 09 22:15:49 riscque.net prosody[21383]: socket: server.lua: accepted new client connection from 27.32.65.246:56867 to 5222
Sep 09 22:15:49 riscque.net prosody[21383]: c2s20bbc10: Client connected
Sep 09 22:15:49 riscque.net prosody[21383]: c2s20bbc10: Client sent opening <stream:stream> to riscque.net
Sep 09 22:15:49 riscque.net prosody[21383]: c2s20bbc10: Sent reply <stream:stream> to client
Sep 09 22:15:49 riscque.net prosody[21383]: c2s20bbc10: Received[c2s_unauthed]: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
Sep 09 22:15:49 riscque.net prosody[21383]: socket: server.lua: we need to do tls, but delaying until send buffer empty
Sep 09 22:15:49 riscque.net prosody[21383]: c2s20bbc10: TLS negotiation started for c2s_unauthed...
Sep 09 22:15:49 riscque.net prosody[21383]: socket: server.lua: attempting to start tls on tcp{client}: 0x2118938
Sep 09 22:15:49 riscque.net prosody[21383]: socket: server.lua: ssl handshake done
Sep 09 22:15:49 riscque.net prosody[21383]: c2s20bbc10: Client sent opening <stream:stream> to riscque.net
Sep 09 22:15:49 riscque.net prosody[21383]: c2s20bbc10: Sent reply <stream:stream> to client
Sep 09 22:15:50 riscque.net prosody[21383]: c2s20bbc10: Received[c2s_unauthed]: <iq id='purple1ca641d8' type='get'>
Sep 09 22:15:50 riscque.net prosody[21383]: stanzarouter: Stanza of type iq from c2s_unauthed has xmlns: jabber:iq:auth
Sep 09 22:15:50 riscque.net prosody[21383]: stanzarouter: Unhandled c2s_unauthed stanza: iq; xmlns=jabber:iq:auth
Sep 09 22:15:50 riscque.net prosody[21383]: c2s20bbc10: Received </stream:stream>
Sep 09 22:15:50 riscque.net prosody[21383]: c2s20bbc10: c2s stream for <27.32.65.246> closed: session closed
Sep 09 22:15:50 riscque.net prosody[21383]: c2s20bbc10: Destroying session for (unknown) ((unknown)@riscque.net)
Sep 09 22:15:50 riscque.net prosody[21383]: c2s20bbc10: Client disconnected: connection closed
Sep 09 22:15:50 riscque.net prosody[21383]: c2s20bbc10: Destroying session for (unknown) ((unknown)@(unknown))
Sep 09 22:15:50 riscque.net prosody[21383]: socket: server.lua: closed client handler and removed socket from list

prosody is version 0.9.0-1 from [community]. lua-cyrussasl is version 1.0.0-2 from the AUR. I know that Cyrus SASL itself isn't the underlying problem, because I have other things (especially postfix) set up to auth against it, and that is working fine.

Is there any easy way to find out, eg, exactly *what* error the SASL prosody mod has when it initializes? Googling prosody error initializing module 'auth_cyrus' on 'localhost' gives no useable results (primarily, the source code of that module).