Upgrade Notes from Kolab 3.4 to 16

The purpose of this document is, to describe the procedure of upgrading a Kolab Goupware installation from a default installed Kolab 3.4 (last “community verison”) to Kolab 16.

Upgrade Procedure

  1. Install the Kolab Groupware repository configuration:

    # cd /etc/yum.repos.d/
    # wget http://obs.kolabsys.com/repositories/Kolab:/16/CentOS_7/Kolab:16.repo
  2. Remove the existing Kolab 3.4 repositories:

    # rm Kolab\:3.4.repo
    # rm Kolab\:3.4\:Updates.repo
  3. Make sure that the packages from the Kolab repositories have a higher priority than eg. the EPEL packages:

    # for f in /etc/yum.repos.d/Kolab*.repo; do echo "priority = 60" >> $f; done
  4. Replace php-mysql with php-mysqlnd:

    # yum shell
    > remove php-mysql
    > install php-mysqlnd
    > run
    (Confirm as requested)
    > exit
  5. Update all:

    # yum -y update


    During the cleanup, you might see the message:

    /var/tmp/rpm-tmp.TUmak9: line 1: fg: no job control
    Cleanup    : cyrus-imapd-2.5-108.3.el7.kolab_3.4.x86_64                                               347/404
    /var/tmp/rpm-tmp.K51Mal: line 2: fg: no job control
    warning: %postun(cyrus-imapd-2.5-108.3.el7.kolab_3.4.x86_64) scriptlet failed, exit status 1
    Non-fatal POSTUN scriptlet failure in rpm package cyrus-imapd-2.5-108.3.el7.kolab_3.4.x86_64

    This is a warning, and the Cyrus-imapd package will be updated. This can be checked after the update with the command:

    # rpm -qv cyrus-imapd
  6. Drop the policy_result table from MySQL.

Updating the Configuration

After upgrading the packages to Kolab 16 repository, the configuration needs to be updated.

  1. Configure the new module “Guam”:

    # setup-kolab guam
  2. Configure the new module “Manticore”:

    # setup-kolab manticore


    If the Kolab 3.4 installation was a standard installation with no changes to the defaults, then the following 2 commands can be run at no risk (The correct password for the current roundcube database user is still needed for verification).

    However, if changes were made to the defaults, the original configuration should be copied off for later compare with the newly written configuration.

  3. Update the roundcube configuration:


    As setup-kolab is unable to write to the already existing mysql database, an error message will show:

    ERROR 1007 (HY000) at line 1: Can't create database 'roundcube'; database exists
    ERROR 1050 (42S01) at line 8: Table 'session' already exists

    The new and updated config file will however be written and restart the appropriate services.

    The correct password for the current roundcube database user is still needed for verification.

    # setup-kolab roundcube
  4. Update the imap configuration:

    # setup-kolab imap