Product SiteDocumentation Site

Chapter 3. Installation

3.1. Kolab Server Installation
3.2. Repository Configuration
3.2.1. Installation with APT Packages
3.2.2. Installation with RPM Packages
3.3. Full default installation on a single server
3.4. Packagelist
The Kolab community provides APT and RPM packages for most commonly used Linux distributions. Please see Section 3.2.1, “Installation with APT Packages” and Section 3.2.2, “Installation with RPM Packages” for more information.

3.1. Kolab Server Installation

To get a fully working Kolab installation all of the components listed in Chapter 2, Overview need to be installed and the system needs to be prepared according to the instructions listed in Chapter 1, Preparing the System.
The Kolab community provides APT and RPM packages for most commonly used Linux distributions. To get a fully working Kolab server on a single system, please install the “kolab-groupware” meta-package which will install all components, and run the setup script on a single system.
The default installation assumes that all components are installed on the same system.
If you have a distributed deployment or want non default components, please see Section 3.2.1, “Installation with APT Packages” and Section 3.2.2, “Installation with RPM Packages” for more information.
For help with your deployment please refer to the “Deployment Guide”.

3.2. Repository Configuration

Kolab provides packages in extra repositories, therefore these repositories need to be configured first.

3.2.1. Installation with APT Packages

Important

APT packages for Kolab 3.0 on Debian Wheezy are a work in progress.
APT packages are provided for the following GNU/Linux distributions, and distribution versions:
Table 3.1. APT Packages Distribution Support
Distribution Information EOS / EOL Date
Name CodeName Version Architectures
Debian Wheezy (testing) 7.0 i386, amd64 T.B.D.
Debian Sid (unstable) N/A i386, amd64 T.B.D.

3.2.1.1. Debian

  1. For Kolab 3.0 software packages for Debian Wheezy, add the following two lines to /etc/apt/sources.list.d/kolab-3.0.list: 
    deb http://mirror.kolabsys.com/pub/debian/kolab-3.0/ wheezy release updates
deb-src http://mirror.kolabsys.com/pub/debian/kolab-3.0/ wheezy release updates

    Updates in Testing Phase and Packages in Development

    Optionally, enable the updates-testing and development components for newer, but less stable packages.
    For other versions of the Debian distribution, please replace wheezy with the corresponding distribution codename.
  2. To ensure the Kolab packages have priority over the Debian packages, such as must be the case for PHP as well as Cyrus IMAP, please make sure the APT preferences pin the mirror.kolabsys.com origin as a preferred source. Put the following in /etc/apt/preferences.d/kolab: 
    Package: *
Pin: origin mirror.kolabsys.com
Pin-Priority: 501
  3. Update the repository metadata: 
    # apt-get update
  4. Start the installation of the base package as follows: 
    # aptitude install kolab
  5. Verify the packages from the Kolab mirror have priority over the packages from the stock Debian repositories: 
    # apt-cache policy cyrus-imapd
  6. When asked to confirm you want to install the package and its dependencies, press Enter.
  7. When asked to confirm you want to continue installing the packages of which the integrity nor source can be securely verified, press y then Enter.

3.2.1.2. Ubuntu

  1. For Kolab 3.0 software packages for Ubuntu Lucid, add the following two lines to /etc/apt/sources.list: 
    deb http://mirror.kolabsys.com/pub/ubuntu/kolab-3.0/ lucid release updates
deb-src http://mirror.kolabsys.com/pub/ubuntu/kolab-3.0/ lucid release updates
    For other versions of the Ubuntu distribution, please replace lucid with the corresponding distribution codename.
  2. To ensure the Kolab packages have priority over the Ubuntu packages, such as must be the case for PHP as well as Cyrus IMAP, please make sure the APT preferences pin the mirror.kolabsys.com origin as a preferred source. Put the following in /etc/apt/preferences: 
    Package: *
Pin: origin mirror.kolabsys.com
Pin-Priority: 501

3.2.1.3. Troubleshooting the APT Package Manager

3.2.1.3.1. Broken Packages
If you get an error similar to, for example: 
test90-1:~# apt-get install kolab
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 kolab:    Depends: postfix (>= 2.4) but it is not going to be installed
            Depends: postfix-ldap (>= 2.4) but it is not going to be installed
E: Broken packages
The error is not caused by broken packages, but a broken package manager that cannot install exim and postfix in parallel.
Solution
First remove any non-postfix MTA you may have installed, which in a default Debian installation is probably exim.
To remove exim, execute the following with superuser privileges: 
# apt-get remove exim4 exim4-base exim4-config exim4-daemon-light
Then continue installing Kolab: 
# aptitude install kolab

3.2.2. Installation with RPM Packages

RPM packages are being provided for the following Linux distributions and versions:
Table 3.2. RPM Packages Distribution Support
Distribution Information EOS / EOL Date
Name CodeName Version Architectures
CentOS - 6 i386, amd64 Approximately Q4, 2017
Fedora Verne 16 i386, amd64 Q2, 2013
Fedora Beefy Miracle 17 i386, amd64 Q4, 2013
Red Hat Enterprise Linux Santiago 6 i386, amd64 Approximately Q4, 2017

Before the installation, it is necessary to install the configuration for the Kolab software repositories.

3.2.2.1. Using the Priorities YUM Plugin to Avoid Package Conflicts

Since any given package may, at any time, be or become available to the system through both the Kolab repositories as well as through the regular distribution repositories, to avoid the risk of switching back and forth between the two different versions continuously, by mistake or by accident, we recommend you use the following procedure including employing YUM repository priorities to eliminate the risk of running in such problems in the future.
Consider installing the yum-priorities (Enterprise Linux 5) or yum-plugin-priorities package (all other platforms) to avoid such conflicts.
Procedure 3.1. Installing and Configuring YUM priorities

  1. Enterprise Linux 6

    The yum-plugin-priorities is available from the EPEL package repository. Please install it: 
    # yum install yum-plugin-priorities

  2. Fedora

    The yum-plugin-priorities is available in the standard repositories. Please install it: 
    # yum install yum-plugin-priorities
  3. The repositories that have been installed using the kolab-3.0-community-release package(s) have a pre-configured priority of 50. The default repository priority is 99. This will set the correct priorities, unless you have repositories configured other than the base operating system repositories (not including 'addons' and 'extras' on CentOS platforms), EPEL and the Kolab Groupware repositories. Should the system happen to already make use of YUM priorities, please make sure the Kolab repositories have the appropriate priority.

3.2.2.2. Configuration Considerations for Additional Repositories

Many additional third party software repositories exist, some of which provide packages also provided as part of the Red Hat Enterprise Linux or CentOS standard package repositories, the EPEL add-on repository Kolab Groupware requires, and/or the Kolab Groupware software repositories itself.
Acceptable third party add-on software repositories include:
  • EPEL (required)
  • RPM Fusion (optional)
Repositories that the system must not be using, include:
  • RPM Forge
  • Webmin
Should the repository you wish to use not be listed here, please consult the Kolab Development mailing list.

3.2.2.3. CentOS

For full instructions on installing Kolab Groupware on CentOS, please refer to the instructions in Section 3.2.2.5, “Red Hat Enterprise Linux”.

Disable 'addons' and 'extras' repositories

Please be aware that on CentOS, you will need to disable the 'addons' and 'extras' repositories, as they contain packages not part of the Enterprise Linux base operating system.
The disable these repositories, edit /etc/yum.repos.d/CentOS-Base.repo and append a setting enabled=0 to sections [addons] and [extras], or delete the sections entirely.

3.2.2.4. Fedora

The Kolab software repositories for Fedora ship two so-called -release packages:
  1. kolab-3.0-community-release
    Depending on the version of Fedora, find the -release package at:
  2. kolab-3.0-community-release-development
    You can install the kolab-3.0-community-release-development package using YUM, after having installed the kolab-3.0-community-release package; 
    # yum install kolab-3.0-community-release-development
Install this package using the following command: 
# wget http://url/to/rpm
# yum localinstall --nogpgcheck /path/to/rpm

3.2.2.5. Red Hat Enterprise Linux

The EPEL repository is required for Kolab Groupware on Red Hat Enterprise Linux. Install the EPEL repository using the following procedure:
Procedure 3.2. Installing the epel-release Package
  1. Depending on the version of Red Hat Enterprise Linux, install the package as it is listed on the following page:
  2. Install this package using the following command: 
    # wget http://url/to/rpm
# yum localinstall --nogpgcheck /path/to/rpm
The Kolab software repositories for Red Hat Enterprise Linux ship two so-called -release packages:
  1. kolab-3.0-community-release
    Depending on the version of Enterprise Linux, find the -release package at:
  2. kolab-3.0-community-release-development
    You can install the kolab-3.0-community-release-development package using YUM, after having installed the kolab-3.0-community-release package; 
    # yum install kolab-3.0-community-release-development

3.2.2.6. Repository Package Stages

Stable Software
Stable software, versions of packages deemed ready for general availability and production environments are distributed through two repositories, release and updates. These repositories are configured on the system, and enabled by default, by installing the kolab-3.0-community-release package;
Stable Software Currently in Testing
The kolab-3.0-community-release package also installs a repository through which upcoming updates currently in their testing phase are distributed. This repository is called updates-testing, and is not enabled by default. Through Kolab Systems and/or community support channels, you may be asked to test an update distributed through the updates-testing repository to see if it fixes a bug you have reported. You would then, typically, temporarily enable the updates-testing repository by supplying the --enablerepo=kolab-3.0-updates-testing command-line option to YUM, overriding the system configuration file setting.
Example 3.1. Installing an Update from updates-testing
# yum --enablerepo=kolab-3.0-updates-testing update [package]

Software Currently in Development
Software that is currently in development for the product series you are running (in this case, series 3.0) is available through the so-called development repository. This software is considered unstable. By default, you will not have the package installed that provides the configuration for this repository; the kolab-3.0-community-release-development package. Installing this package will cause the development repository to be enabled by default.

3.3. Full default installation on a single server

If you want a default installation with all components on a single server, please run: 
# yum install kolab
Installing this meta-package will install all needed software components.
Once the installation is complete, you can continue with the configuration process as described in Chapter 4, Configuration.
Alternatively you can install each component individually, which will give you the same result.

3.4. Packagelist

The following packages are available to install the individual components. Please use your distributions package management system to install them.
The default meta-package will install the default component. The alternative package is an alternative to the default component. Optional packages provide extra functionality which is not needed for a standard installation.
Table 3.3. Packages
Package List Package Description
Package default meta-package alternative package optional packages
Complete Server kolab - - A meta package to install all default components.
LDAP kolab-ldap - - The LDAP component (389 Directory Server).
IMAP kolab-imap - - The IMAP component (Cyrus IMAP).
MTA kolab-mta - - The MTA component (Postfix by default).
Webadmin kolab-webadmin - - -
Webclient kolab-webclient - - -