Kolab 3.4: Disaster

[Stefan Froehlich]

Since all those tables already exists I assume my DB is on the latest 
level. However, I tried to run this script and it gave me

/usr/share/roundcubemail/plugins/libkolab/SQL# 
/usr/share/roundcubemail/bin/updatedb.sh --dir 
/usr/share/roundcubemail/plugins/libkolab/SQL --package libkolab
Updating database schema (2013100400)... ERROR: [1050] Table 
'kolab_folders' already exists (SQL Query: CREATE TABLE `kolab_folders` (
   `folder_id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
   `resource` VARCHAR(255)  NOT NULL,
   `type` VARCHAR(32) NOT NULL,
   `synclock` INT(10) NOT NULL DEFAULT '0',
   `ctag` VARCHAR(40) DEFAULT NULL,
   PRIMARY KEY(`folder_id`),
   INDEX `resource_type` (`resource`, `type`)
) /*!40000 ENGINE=INNODB */ /*!40101 CHARACTER SET utf8 COLLATE 
utf8_general_ci */)[FAILED]
Error 500: Error in DDL upgrade 2013100400: [1050] Table 'kolab_folders' 
already exists
root at FFA-SRV-01:/usr/share/roundcubemail/plugins/libkolab/SQL# 
/usr/share/roundcubemail/bin/updatedb.sh --dir 
/usr/share/roundcubemail/plugins/libkolab/SQL --package libkolab
Updating database schema (2013100400)... ERROR: [1050] Table 
'kolab_folders' already exists (SQL Query: CREATE TABLE `kolab_folders` (
   `folder_id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
   `resource` VARCHAR(255)  NOT NULL,
   `type` VARCHAR(32) NOT NULL,
   `synclock` INT(10) NOT NULL DEFAULT '0',
   `ctag` VARCHAR(40) DEFAULT NULL,
   PRIMARY KEY(`folder_id`),
   INDEX `resource_type` (`resource`, `type`)
) /*!40000 ENGINE=INNODB */ /*!40101 CHARACTER SET utf8 COLLATE 
utf8_general_ci */)[FAILED]
Error 500: Error in DDL upgrade 2013100400: [1050] Table 'kolab_folders' 
already exists

BTW: Table kolab_folders contains heaps of data. 35556 rows and I have 
only 5 mailboxes.

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