Last time I came up with a problem with concernin MySQL authorization with stored procedures. Timo helped me get going by with modified client_flags (MULTISTATEMENT keyword).<br> <br>Now all it happened again but from another way. My stored proce for MySQL is causing fillowing error:
<br> <br>"Oct 21 12:39:22 haos dovecot: auth-worker(default): sql(user,192.168.X.X): Password query fai led: Commands out of sync; you can't run this command now"<br><br>Looks like it is partly mysql-5.0.26 thing because of this:
<a href="http://dev.mysql.com/doc/refman/5.0/en/commands-out-of-sync.html">http://dev.mysql.com/doc/refman/5.0/en/commands-out-of-sync.html</a><br> <br>On the other hand with my previous mysql installation (mysql-5.0.24-r1
) this error is gone (I checked by downgrading).<br>My dovecot-sql.conf:<br><br>driver = mysql<br>connect = host=/var/run/mysqld/mysqld.sock dbname=mailbase user=mailuser password=******** client_flags=65536<br>#655536 is equivalent of CLIENT_MULTI_STATEMENTS flag
<br>#yes, I still insist on using stored proc for authorization. This gives me few usefull features I like. <br>password_query = call Authenticat('%u', '%n', '%d')<br><br>With this config on mysq-5.0.26 I get<br> "...Commands out of sync; you can't run this command now..."
<br>but not on mysql-5.0.24-r1.<br>Personally I think mysql guys changed something; I can't tell what and why (changelog review?)<br>Maybe you guys know what it was? <br clear="all"><br>-- <br>Chaos greets U