Kolab 3.4 on Debian Wheezy experience.

[Markelov Alexander]

Some experience about Kolab 3.4 on Debian Wheezy after upgrade from 
Kolab 3.3

1. You need to look after for kolab_cache_* tables in the roundcube DB. 
Sometimes they grow!  If something wrong - use 
http://git.kolab.org/roundcubemail-plugins-kolab/tree/plugins/libkolab/SQL/mysql.initial.sql 
from https://issues.kolab.org/show_bug.cgi?id=4850
2. Best practice is use option - "innodb_file_per_table" in MySQL. If 
something go wrong with kolab_cache_*, tables only 
"innodb_file_per_table" option allow You to reclaim disk space. 
https://dev.mysql.com/doc/refman/5.0/en/innodb-multiple-tablespaces.html 
https://rtcamp.com/tutorials/mysql/enable-innodb-file-per-table/
3. PHP garbage collector switched off in Debian by default, and maybe is 
broken.

cat /etc/php5/apache2/php.ini | grep session.gc_probability
session.gc_probability = 0

You need to think about it and clean garbage manually like:

cat /etc/cron.daily/rc-session-clean
#!/bin/bash
mysql -v -v --user=roundcube --password=roundcubepassword 
--database=roundcube --execute="DELETE FROM session WHERE changed < 
NOW() - INTERVAL 1 DAY"
/usr/share/roundcubemail/bin/gc.sh

First clean the roundcube.session table.
Second clean roundcube.cache_* tables.

-- 
Markelov Alexander - IT/Net engineer
http://13.net.ru
xmpp:deep at 13.net.ru
ICQ 13372829