Kolab2 Installation - Source

From Kolab Wiki

Jump to: navigation, search

You find the Kolab3 installation page here.

The installation method described here is the default installation variant for Kolab.

It should take about three hours of time on a machine with average speed.

Kolab makes use of OpenPKG job description to provide a supportable base on a wide variety of platforms. For alternatives you can check the Kolab Installation Overview page. There are also some Open-Office documents available in the Kolab-CVS repository that also describe the Kolab server installation.

This wikipage might be outdated: Before following the instruction given on this page check that it has been updated since the last server release mentioned on the Kolab home page! If not look at the 1st.README file in the source directory of the latest release. That one is guaranteed to be maintained for each release. In fact it is recommended to always read through the 1st.README file as it might contain information which is missing here.



Download a snapshot

There are beta snapshots available from the mirrors. Just fetch all the files from the latest release and save them to a temporary directory on your local machine. This temporary directory needs to be world readable. You are advised to use the /tmp directory! The following would fetch the Kolab-2.2.4 release:

mkdir /tmp/kolabtemp
cd /tmp/kolabtemp
wget -r -l1 -nd --no-parent http://files.kolab.org/server/release/kolab-server-2.2.4/sources/

You can check the integrity of the downloaded files with:

gpg --keyserver wwwkeys.pgp.net --recv-key 5816791A
gpg --verify SHA1SUMS.sig
sha1sum -c SHA1SUMS

Instead of using gpg --keyserver wwwkeys.pgp.net --recv-key 5816791A you can also import the key from https://www.intevation.de/~thomas/gpg_pub_key.asc

Install Kolab in the OpenPKG environment

The default is to install to the directory /kolab:

mkdir /kolab

For a fresh install /kolab needs to be an empty directory with at least 1.5GB of free disk space. If the directory does not yet exist, it will be created automatically.

Alternatively, you can create a local directory /usr/local/kolab and merely symbolically link /kolab to it. In that case all files will be stored in /usr/local/kolab (but will appear to be running from within the /kolab directory):

mkdir /usr/local/kolab
ln -s /usr/local/kolab /kolab

A third option is to mount /kolab on a separate disk or raid array (but please do NOT use an NFS mounted drive.). For example, if you have an empty ext3 partition at /dev/sda3, you would first create the /kolab directory (as above), then edit /etc/fstab to include the line:

/dev/sda3  /kolab  ext3  defaults,rw 0 0

and then reboot.

Once you have downloaded all the files, check the following:

  • that you have bison and flex installed
  • that you have SELinux turned off (or set to non-enforcing) if your system has SELinux.
  • that you have a gcc, make, libtool, automake and autoconf installed.
  • that the following names are not in /etc/passwd or /etc/groups, as OpenPKG will want to create them: kolab, kolab-r, kolab-n

Then run install-kolab.sh as a privileged user (usually root) to set up Kolab in the OpenPKG environment:

sh install-kolab.sh 2>&1 | tee /root/kolab-install.log

or make the script executable and run it directly like this:

chmod +x install-kolab.sh
./install-kolab.sh 2>&1 | tee /root/kolab-install.log

Please read the installation notes for your distribution.

This will start the installation. It rebuilds the OpenPKG sources for your machine, and builds/installs rpms with a special OpenPKG rpm tool (this way the OpenPKG rpms do not conflict with your current systems rpms and are kept on a different database). It can take a couple of hours to finish this installation, so fetch some more coffee and check every now and then to see how its doing.

If you do not want to install the Horde groupware client and/or the free/busy view tool, you can drop the flag "-H" and/or "-F".

The command output will be logged to kolab-install.log.

The total installation needs around 750MB (this is without the sources, add another 265MB if you have the sources on the same partition).

If the installation goes smoothly, you should end up with a summary of the installed packages.
If something goes wrong, you should consult the troubleshooting section that deals with installation problems.

Initial configuration

You now should have a /kolab directory, but you are not quite finished. You still need to configure the server for your specific network conditions. kolab_bootstrap will allow you to bootstrap the system and specify required information such as your mail domain etc. Finally openpkg rc will be used for starting and stopping the Kolab server. But lets start with the bootstrap first:

/kolab/sbin/kolab_bootstrap -b

The script will check your available network ports to see if there are any conflicting services (such as another web server, a mail transfer agent or a LDAP database) already running in the base system on your machine. The script will die if there are any since you can't have any of these services running on your wisata pulau tidung machine and simultaneously try to run it in your OpenPKG-Kolab environment. If there are conflicting services, stop them, and make sure they do not restart on reboot or based on other conditions. If all required network ports are available, the bootstrap script will ask some questions to configure your server. The questions should be self explanatory. Go through this setup carefully to set the basic configuration of your Kolab server.

Start using Kolab

After bootstrapping you can finally start your system:

/kolab/bin/openpkg rc all start

This starts all the Kolab services and you should see amavisd, apache, clamav, imapd, kolab, openldap, openpkg, postfix, proftpd, sasl, spamassassin start.

All done! You can now go to https://hostname.of.machine/admin/ (replace hostname.of.machine with your machines complete domain name) and log in as the user manager and the password you supplied during bootstrapping.

Check the additional documentation

In addition there are some documents in the Kolab-CVS repository sales associate job description that you might wish to read.

If your server works as expected you might also wish to read about configuring a client.

Personal tools