Kolab 3.4: Disaster
Stefan Froehlich
stefan at ffa-it.com.au
Sat Mar 21 03:20:52 CET 2015
Ok, I went down the path to completely reinstall Debian and Kolab. I
have to say at the current stage all mentioned problems have been solved
so far. It looks lie at least the nasty heavy disk I/O bug doesnt exist
anymore. This bug also drained the batteries of our mobile phones very
quickly. In addition the growing database problem doesn't exist on a
fresh install. This leads to the conclusion that the upgrade path is
somehow broken.
MfG Stefan Fröhlich
42 ;-)
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
More information about the users
mailing list