Displaying 2 results from an estimated 2 matches for "sasl_server_reply_master_fail".
Did you mean:
sasl_server_reply_master_failed
2008 Sep 30
5
Corrupted transaction log file / record size too small
I recently upgradeded dovecot on one of our servers from version 1.0.10
to version 1.1.3. Ever since, we've been seeing occasional errors
similar to this sequence (with the username and IP addresses elided):
Sep 30 00:09:56 alcor dovecot: pop3-login: Login: [4954], XXXX, NNN.NNN.NN.NNN
Sep 30 00:09:56 alcor dovecot: wrapper[5006]: pop3, XXXX, NNN.NNN.NN.NNN
Sep 30 00:09:56 alcor
dovecot-auth: sockbuf.c:91: ber_sockbuf_ctrl: Assertion `( (sb)->sb_opts.lbo_valid == 0x3 )' failed.
2008 Jan 28
2
dovecot-auth: sockbuf.c:91: ber_sockbuf_ctrl: Assertion `( (sb)->sb_opts.lbo_valid == 0x3 )' failed.
...niffit gives me the
proof that i'm receiving proper data from AD LDAP. but there is
another problem:
Jan 28 13:11:13 gentoo dovecot: imap-login: file
client-authenticate.c: line 200 (sasl_callback): assertion failed:
(!client->destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR ||
reply == SASL_SERVER_REPLY_MASTER_FAILED)
[...]
Jan 28 13:36:50 gentoo dovecot: auth(default): dovecot-auth:
sockbuf.c:91: ber_sockbuf_ctrl: Assertion `( (sb)->sb_opts.lbo_valid
== 0x3 )' failed.
it seems that Dovecot cannot insert received data into the environment
variables (???)
--
Maciej Paczesny
maciunio2 at gmail.com
**...