was: smtp policy mysql bug ?

[Daniel Hoffend]

Identified, but not yet committed

In my opinion it's a non-closed transactions that is blocking other 
concurrent database calls.

You've 2 choices to get a workaround
1) apply the hotfix to the python script (that's at least what I did)
2) Change the mysql table from innodb to something that doesn't support 
transactions like myisam or memory

Here are the current tickets for this problem:
https://issues.kolab.org/show_bug.cgi?id=3553
https://issues.kolab.org/show_bug.cgi?id=3567

I'm waiting that some of kolab looks at it and maybe applies the fix.


--
Regards
Daniel

------ Originalnachricht ------
Von: "Sebastian Walter" <mail at swalter-it.com>
An: users at lists.kolab.org
Gesendet: 05.09.2014 14:55:16
Betreff: was: smtp policy mysql bug ?

>Hi all,
>
>I'm experiencing the same problems as described in this thread:
>
>http://lists.kolab.org/pipermail/users/2014-March/thread.html#16917
>
>Has this been solved in the meantime? If yes, how?
>
>These are the symptoms:
>
>After some time running, sending mails doesn't work anymore.
>In /var/log/maillog, I get entries like these:
>
>postfix/smtpd[24806]: warning: premature end-of-input on
>private/recipient_policy_incoming while reading input attribute name
>postfix/spawn[24807]: warning: command
>/usr/libexec/postfix/kolab_smtp_access_policy exit status 1
>
>At the same time, mariadb is locked.
>
>The only way to get the system back running, is to restart mysqld and
>then empty the policy_result table manually.
>
>But after half a day or so, the sending of mails locks again.
>
>Any help would be great.
>
>Regards, Sebastian
>_______________________________________________
>users mailing list
>users at lists.kolab.org
>https://lists.kolab.org/mailman/listinfo/users