Kolab 3.4: Disaster

Franz Skale i.bin at dah.am
Wed Mar 18 17:04:01 CET 2015



Hi Stefan,
i have some troubles with calendar entries spreading over two days when
defining a whole day event.
This is with version 3.3. ;-)

I started my upgrade yesterday and stopped when upgrading cyrus.
After cyrus has been upgraded,  wonderful errors are filling up my
pykolab.log.
So, only cyrus changed and that caused a complete malfunction of the
sqlalchemy part of the auth caching mech ?
I'm a little bit speecheless. I downgraded my complete system using a
btrfs snapshot.
The error:
2015-03-18 16:58:08,067 pykolab.auth ERROR Authentication cache failed:
StatementError("Can't reconnect until invalid transaction is rolled back
(original cause: InvalidRequestError: Can't reconnect until invalid
transaction is rolled back)",)
10000 of them.
I started with debug level 9 and all ldap parts are working without errors.
So, where's the origin of this error ?
Using google a found some hints about sql-alchemy and smtp_access_policy
caching.
Perhaps someone has a hint.
For now, i don't upgrade to 3.4.Toooo buggy for me.

Rgds.

Franz



Am 18.03.15 um 15:30 schrieb Stefan Froehlich:
> I ran all scripts manually. Still no change.
>
>
> On 18/03/2015 10:50 PM, dsp3 wrote:
>> Stefan,
>> Try this:
>>
>> /⁠usr/⁠share/⁠roundcubemail/⁠bin/⁠updatedb.sh \
>>    -⁠-⁠dir /⁠usr/⁠share/⁠roundcubemail/⁠plugins/⁠libkolab/⁠SQL \
>>    -⁠-⁠package libkolab
>>
>> This was on Centos 6 system.
>>
>> SQL tables needed updating. My calendar items then re-⁠appeared.
>>
>> On 2015-03-18 12:42, Stefan Froehlich wrote:
>>> Just emptied all calendars, started reconstruct to create cyrus index
>>> files, created a couple of entries. Can see all entries in roundcube.
>>> Can see "some" entries on phone. One entry with recurrence created
>>> five (!!!) entries on the phone.
>>> I think I'll go back to 3.3
>>>
>>> On 18/03/2015 5:54 PM, Stefan Froehlich wrote:
>>>> Hi Folks,
>>>>
>>>> I must say from my point of view the update to 3.4 was a disaster.
>>>> I was finally able to find and work around the growing database
>>>> problem. But some serious problems still exsists and one rendered
>>>> all my calendars useless.
>>>> 1) I'm still experiencing high CPU usage and heavy disk I/O. It is
>>>> somehow related to apache because if I shut it down the disk I/O
>>>> stops.
>>>> 2) Roundcube is horrible slow. Doesn't matter if it runs with or
>>>> without cache in mysql
>>>> 3) In Calendar it started to show double, triple, multiple calendar
>>>> entries on our mobile phones. In Roundcube there is only one entry
>>>> but it is showing up with multiple entries on android. Looking into
>>>> the folder with Thunderbird there were hundreds of items, much more
>>>> than entries in Roundcube.
>>>>
>>>> MfG Stefan Fröhlich
>>>> 42 ;-)
>>>> _______________________________________________
>>>> users mailing list
>>>> users at lists.kolab.org
>>>> https://lists.kolab.org/mailman/listinfo/users
>>>
>>> _______________________________________________
>>> users mailing list
>>> users at lists.kolab.org
>>> https://lists.kolab.org/mailman/listinfo/users
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users
>
> _______________________________________________
> 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/pkcs7-signature
Size: 4254 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.kolab.org/pipermail/users/attachments/20150318/68dc97a1/attachment.p7s>


More information about the users mailing list