Allocating sasl connection state: generic failure
Dan White
dwhite at olp.net
Mon Feb 13 18:11:48 EST 2012
On 02/13/12 23:38 +0100, Per olof Ljungmark wrote:
>Hi,
>
>I am in the process of upgrading my laptop from FreeBSD-8 to 9-STABLE,
>thus also rebuilding a LOT of ports.
>
>I now notice that Postfix stopped to work with SASL AUTH (TLS and
>unencrypted is fine), and it appears that the problem is with
>cyrus-sasl2. I've gotten as far as building the sample server and
>client and when I try to start sample-server it returns
>"sample-server: Allocating sasl connection state: generic failure"
>
>Could someone please with better knowledge take a look at the trace
>below (follow the link) and possible find out where the problem lies?
>Most likely something I screwed up myself...
>
>The command was
>ktrace -f ./ktrace ./sample-server -s host -p ../plugins/.libs
>but I get the same result regardless of options
>
>-----
>Attachments
>http://webmail.inter-sonic.com/imp/attachment.php?u=peobsd&t=1329166070&f=cyrus-sasl2-ktrace
Which version of cyrus sasl?
This page briefly mentions the error in conjunction with sample-client:
http://www.cyrussasl.org/docs/cyrus-sasl/2.1.25/gssapi.php
I see what looks like DNS activity just before the error is printed. You
can try restricting which shared libraries are loaded to see if you can
narrow the problem down to a particular plugin:
cat >> /usr/lib/sasl2/sample.conf <<EOF
mech_list: plain
auxprop_plugin: sasldb
EOF
(for sample-server)
Adjust the path accordingly (your --with-configdir=DIR). The same config
could be applied to your postfix sasl smtpd.conf for testing.
--
Dan White
More information about the Cyrus-sasl
mailing list