Kolab2 Installation - Binary

From Kolab Wiki

Revision as of 14:42, 5 August 2010 by Ffws (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Kolab makes use of OpenPKG to provide a supportable base on a wide variety of platforms. Installation of the environment can be done from source with a script called obmtool (OpenPKG poor man's Boot, Build & Management Tool).

The installation method described here is not the default installation variant for Kolab since you need binary packages matching your platform

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.

Contents

Installation from binaries

Read the 1st.README in the install directory before you start install!

Kolab Server 2.1.*

  • Download all packages of a 2.1.*-version from a mirror in a local directory.
  • You can check the integrity of the downloaded files with:
gpg --verify MD5SUMS
md5sum -c MD5SUMS
  • Change into that local (and writable) directory and run (as root):
./obmtool kolab 2>&1 | tee kolab-install.log

obmtool may fail the first time due to some unresolved dependencies, repeat the obmtool some more time to get it going. You are fine as long as the number of installed packages increases ;-)

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

Kolab Server 2.2.* (beta)

  • Download all packages of a current (beta) version from a mirror in a local directory.
  • You can check the integrity of the downloaded files with:
gpg --verify MD5SUMS
md5sum -c MD5SUMS
  • Change into that local (and writable) directory and run (as root):
./install-kolab.sh -H -F 2>&1 | tee kolab-install.log

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.


Kolab Server 2.2.1 (beta)

  • Download all packages of a current (beta) version from a mirror in a local directory.
  • You can check the integrity of the downloaded files with:
gpg --keyserver hkp://subkeys.pgp.net --recv-key 5816791A
gpg --verify SHA1SUMS.sig
sha1sum -c SHA1SUMS
  • Change into that local (and writable) directory and run (as root):
sh install-kolab.sh 2>&1 | tee /root/kolab-install.log

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


Kolab Server 2.2.4

  • Download all packages of a current release from a mirror in a local directory, for example:
mkdir /tmp/kolabtemp
cd /tmp/kolabtemp
wget -r -l1 -nd --no-parent http://ftp.gwdg.de/pub/linux/kolab/server/release/kolab-server-2.2.4/ix86-debian5.0/
  • You can check the integrity of the downloaded files with:
gpg --keyserver hkp://subkeys.pgp.net --recv-key 5816791A
gpg --verify SHA1SUMS.sig
sha1sum -c SHA1SUMS
  • Change into that local (and writable) directory and run (as root):
sh install-kolab.sh 2>&1 | tee /root/kolab-install.log

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


Kernel considerations

Some binaries (in particular the debian 3.1 binaries distributed on the Kolab website) are build on a 2.6 kernel, and will not work on a 2.4 kernel because OpenLdap uses kernel calls not available on 2.4 kernels. If, when running bootstrap, you get the following error :

could not connect ldap server ldap://127.0.0.1:389/ 

Then this may be the case. Type

uname -a

to see you kernel version. Note that the basic Debian 3.1 comes with a 2.4 kernel ; you will need to switch to unstable and upgrade your kernel.


Some binary rpms can be removed

A working kolab installation does not need all of the RPMs were used to build kolab from scratch. In other words packages such as bison, file, flex, make, etc do not seem to be required to run kolab. Therefore, these can therefore be removed from the system.

alias kpm="/kolab/bin/openpkg rpm"
alias rckolab="/kolab/bin/openpkg rc"

Now remove the redundant rpms:

kpm -e automake autoconf bison dbtool dcron file flex gmp make patch sed vim sharutils texinfo

Please check kolab still seems to work fine:

rckolab all stop
rckolab all start

Please note that the binary rpms are needed again (to satisfy obmtool), when a update is released and those update(s) are to be installed from source.


Using binary RPMs

This is just an idea, and has not been tested. Provide feedback in case you tested this

If one can obtain binary kolab rpms, for example from a friendly fellow distribution user, one could probably skip a big part of the obmtool installation process.

Copy the binary openpkg rpm only, into the directory /kolab/RPM/PKG. Add obmtool and obmtool.conf. Make sure obmtool is executable. Then you can just start it (./obmtool kolab). Obmtool will fail with missing packages once the openpkg rpm has been installed.

Now move on to the rest of the binary kolab rpms and have those installed with:

/kolab/bin/openpkg rpm -ivh <the many kolab rpms>

As mentioned before not all rpms must be installed. The rpms listed in the section Some binary rpms can be removed above do not need to be installed.

obmtool:ERROR:

I did try this but didn't get far. Here is the error I am getting:

 server2:/usr/openpkg/RPM/PKG#  ./obmtool kolab
 ---- boot/build server2.orces.com %kolab ----
 obmtool:NOTICE: did not find openpkg/rpm executable. Checking/fetching binary sh.
 obmtool:NOTICE: did not find binary sh. Checking/fetching source sh.
 obmtool:ERROR: please download ./openpkg-2.2.2-2.2.2.src.sh to /kolab/RPM/PKG/ manually and restart obmtool
 server2:/usr/openpkg/RPM/PKG#

That package I don't think exists, I looked everywhere. The I tried the newest version (openpkg-2.5.0-2.5.0.src.sh) but I get the same error


I met the same problem (Ubuntu), you put RPM files to /kolab/RPM/PKG, then run:

/kolab/bin/openpkg rpm -ivh <the many kolab rpms>

it should be OK


I don't know why they can't make the manual a bit clearer. It is actually pretty easy to install. First I thought I had to install openpkg before I can install Kalab but you don't the obmtool takes care of that. Just follow my easy step by step manual: How I did it - This is NOT a binary installation. For a more detailed source installation howto , try Kolab2 Installation - Source

--TaMeR 13:18, 2 April 2006 (UTC)

Personal tools