Update 3.1->3.3 Authentication cache failed

Daniel Hoffend dh at dotlan.net
Sun Sep 14 23:16:25 CEST 2014


Hei Torsten

There was a bug in the pykolab package that was preventing the 
kolab_smtp_access_policy to fail if cache was enabled.

Bug report:
https://issues.kolab.org/show_bug.cgi?id=2661

Fix:
http://git.kolab.org/pykolab/commit/?id=8517e1d8ca37d1d4f9fb649a91e222de0d83f59b

I've pushed the fix has already to the Kolab:3.3:Updates repo last 
night.

Feel free to update your packages (in this case pykolab). Feel free to 
unconfigure the cache_uri (kolab.conf). Small systems can easily keep up 
without the caching.

--
Regards
Daniel Hoffend


------ Originalnachricht ------
Von: "webmaster zigann.de" <webmaster at zigann.de>
An: users at lists.kolab.org
Gesendet: 14.09.2014 19:17:38
Betreff: Update 3.1->3.3 Authentication cache failed

>Hallo,
>
>i have a running Kolab 3.1 on CentOS 6.5 and updated to version 3.3. 
>The system works but is very slow and in calendar view not usable. I 
>get in /etc/kolab/pykolab.log a lot of errors, i never had before:
>
>2014-09-14 19:08:50,834 pykolab.auth ERROR Authentication cache failed: 
>InvalidRequestError('The transaction is inactive due to a rollback in a 
>subtransaction. Issue rollback() to cancel the transaction.',)
>
>Tried already a reinstall of roundcube
>
>yum -y reinstall roundcubemail roundcubemail-plugins-kolab
>
>but this didn't help.
>
>Has anyone the same issue und how can it be fixed?
>
>Regards
>
>Torsten
>_______________________________________________
>users mailing list
>users at lists.kolab.org
>https://lists.kolab.org/mailman/listinfo/users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5714 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20140914/fcc3d40d/attachment.bin>


More information about the users mailing list