wilde: server README.1st,1.69,1.70
cvs at kolab.org
cvs at kolab.org
Fri Feb 1 16:15:05 CET 2008
Author: wilde
Update of /kolabrepository/server
In directory doto:/tmp/cvs-serv20266
Modified Files:
README.1st
Log Message:
Added preliminary upgrade instructions for upgrading from 2.1.
Index: README.1st
===================================================================
RCS file: /kolabrepository/server/README.1st,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -d -r1.69 -r1.70
--- README.1st 3 Dec 2007 17:22:41 -0000 1.69
+++ README.1st 1 Feb 2008 15:15:03 -0000 1.70
@@ -147,13 +147,95 @@
Upgrade from Kolab server 2.1 or before
---------------------------------------
-Instructions for upgrading from Kolab server 2.0 or 2.1 will be added in
-a future version of this document. Additional hints may be available in
-the Kolab wiki: http://wiki.kolab.org/index.php/Kolab2_Upgrading
+Instructions for upgrading from Kolab server 2.0 will be added in a
+future version of this document. This instructions are on upgrading
+from Kolab 2.1.0.
-Direct upgrade from Kolab1 is not supported. We suggest that you back up
-your IMAP store, install Kolab2 and manually recreate user accounts and
-then restore the IMAP data from the backup.
+1. Before upgrading the Kolab server must be stoped:
+
+ # /kolab/bin/openpkg rc all stop
+
+2. Save the current ldap:
+
+ # /kolab/sbin/slapcat > ~/kolab-2.1.ldif
+
+3. Some of the old Kolab packages must be removed to avoid conflicts
+ during the upgrade process:
+
+ # /kolab/bin/openpkg rpm -e --nodeps kolabd-2.1.0-20070510 \
+ kolab-webadmin-2.1.0-20070510 \
+ kolab-horde-fbview-2.1.0-20070420 \
+ kolab-horde-framework-2.1.0-20070420 \
+ kolab-resource-handlers-2.1.0-20070510 \
+ getopt-20051005-2.5.0 \
+ patch-2.5.9-2.5.0 \
+ proftpd-1.3.0rc2-2.5.0 \
+ sharutils-4.5.1-2.5.0
+
+4. A new openpkg version is needed for the upgrade, so we have to
+ install it manually beforehand.
+
+ As root, cd into the directory of kolab server 2.2 binary packages and run:
+
+ # /kolab/bin/openpkg rpm -Uvh \
+ ./openpkg-20071227-20071227.ix86-debian3.1-kolab.rpm
+ # /kolab/bin/openpkg rpm -Uvh \
+ ./openpkg-tools-1.4.6-20071231.ix86-debian3.1-kolab.rpm
+
+ If you don't have binary packages for you platform, you have to build from source.
+ As root, cd into the kolab server 2.2 source directory and run:
+
+ # /kolab/bin/openpkg rpm --rebuild ./openpkg-20071227-20071227.src.rpm
+ # /kolab/bin/openpkg rpm -Uvh \
+ /kolab/RPM/PKG/openpkg-20071227-20071227.<ARCH>-<OS>-kolab.rpm
+ # /kolab/bin/openpkg rpm --rebuild ./openpkg-tools-1.4.6-20071231.src.rpm
+ # /kolab/bin/openpkg rpm -Uvh \
+ /kolab/RPM/PKG/openpkg-tools-1.4.6-20071231.<ARCH>-<OS>-kolab.rpm
+
+ (<ARCH> and <OS> must be replaced by the correct values for your system).
+
+5. Start the standard upgrade (as described above):
+
+ # ./install-kolab.sh -H -F 2>&1 | tee kolab-update.log
+
+6. Before starting the ldap server the database must be restored from
+ the ldif:
+
+ # rm /kolab/var/openldap/openldap-data/*
+ # /kolab/sbin/slapadd -l ~/kolab-2.1.ldif
+
+7. The format of certain databases changed, but as they only hold
+ caches or temporary data they can be simply truncated to zero
+ length:
+
+ # > /kolab/var/imapd/tls_sessions.db
+ [FIX ME: what else?]
+
+8. Remove all *.conf.rpmsave files in the subdirectories of
+ /kolab/etc/ as described above.
+
+ Check /kolab/etc/kolab/kolab.conf and merge content of
+ kolab.conf.rpmsave manually!
+
+9. Start the OpenLDAP, generate the configuration files and start the
+ Kolab server:
+
+ # /kolab/bin/openpkg rc openldap start
+ # /kolab/sbin/kolabconf
+ # /kolab/bin/openpkg rc all start
+
+10. After the success full upgrade some cleanup can be done, by
+ removing obsolete files/directories:
+
+ # rm -r /kolab/etc/resmgr
+ # rm -r /kolab/etc/proftpd
+
+Additional hints may be available in the Kolab wiki:
+http://wiki.kolab.org/index.php/Kolab2_Upgrading
+
+Direct upgrade from Kolab1 is not supported. We suggest that you back
+up your IMAP store, install Kolab2 and manually recreate user accounts
+and then restore the IMAP data from the backup.
Known problems and workarounds
More information about the commits
mailing list