5
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 5:
Line 71: − + Line 19:
Line 85: − + − + + + + + + + + + + + + + + + + + + + + + − As a precausion backup the MySQL database (files we be placed in: /home/e-smith/db/mysql/):+ − signal-event pre-backup − Download the new version from the Zarafa website (rhel4 / i386 / 3 Outlook license (or GPL)) and extract it: http://www.zarafa.com/download-community+ − tar -zxvf zarafa-6.30-rhel4-i386.tar.gz − Stop the Zarafa server:+ − /etc/e-smith/events/actions/zarafa-services-stop − yum localinstall zarafa-6*.rpm zarafa-webaccess-6*.rpm libical*.i386.rpm libvmime*.i386.rpm zarafa-licensed-6*.rpm (last not required for GPL)+ − To regenerate the configuration files:+ − /etc/e-smith/events/actions/zarafa-services start − With this new version some database conversions need to be done, This process must not be interrupted! So we will start the server and tail the server.log for this process to complete:+ − /etc/init.d/zarafa-server start − tail -f /var/log/zarafa/server.log − You'll see some messages about creating and updating tables... wait until you see the 'Startup succeeded' message (see example output below). This process can take a fair amount of time if you have a lot of users and/or big mailboxes, or a few seconds for light use.+ − Start: Adding externid to 'object' table − Done: Adding externid to 'object' table − Start: Creating Single Instance Attachment table − Done: Creating Single Instance Attachment table − Start: Locking multiserver capability − Done: Locking multiserver capability − Start: Creating Addressbook Changes table − Done: Creating Addressbook Changes table − Start: Updating 'singleinstances' table to correct tag value − Done: Updating 'singleinstances' table to correct tag value − Listening for pipe connections on /var/run/zarafa − Listening for TCP connections on port 237 − Startup succeeded on pid 22957 − + − signal-event post-upgrade ; signal-event reboot+ − '''N.B.''' I updated my test box yesterday (07/25). In testing CalDAV from iCal, I found issues in the ical.log and the client would not connect to the calendar. I've raised it on the Zarafa forums. Des Dougan.+ + + + + + + +
Added information on updating php-mapi if upgraded php to version 5.3
=== Zarafa7 on SME8 ===
If you want to test the new Zarafa 7 version on SME8b6: install as described [[Zarafa | here]], download the needed files from [[bugzilla:5789]] => Comment#5 and extract as described, make the following symbolic links and restart apache:
ln -s /lib/libcrypto.so.0.9.8e /usr/lib/libcrypto.so.0.9.8
ln -s /lib/libssl.so.0.9.8e /usr/lib/libssl.so.0.9.8
sv t httpd-e-smith
=== Dependancies ===
Here are links to all the dependencies that I used for version 7.0.1.28479 (free):
libicu - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/libicu-3.6-5.16.i386.rpm
poppler-utils - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/poppler-utils-0.5.4-4.4.el5_6.17.i386.rpm
poppler - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/poppler-0.5.4-4.4.el5_6.17.i386.rpm
hicolor-icon-theme - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/hicolor-icon-theme-0.9-2.1.noarch.rpm
bitstream-vera-fonts - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/bitstream-vera-fonts-1.10-7.noarch.rpm
w3m - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/w3m-0.5.1-18.el5.i386.rpm
If you are upgrading from version 6 you will also need these dependencies:
MySQL-python - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/MySQL-python-1.2.1-1.i386.rpm
mx - http://mirror.centos.org/centos/5/os/i386/CentOS/mx-2.0.6-2.2.2.i386.rpm
- Garth Kirkwood (girkers)
=== Installation ===
To make things a bit more easy for non Zarafa experts, I used this procedure for a clean install.
Get zcp 7.01, unpack, remove the devel packages and install all rpm's:
yum localinstall *.rpm
All packages have dependencies that cannot be resolved if you install only part of the rpm's (as suggested installation instruction for zcp 6.40).
Then install smeserver-zarafa. I could not retrieve this file from the smevdev repository (sme8 uses another one?).
Get it manually and install:
wget http://ftp.nluug.nl/os/Linux/distr/smeserver/releases/7/smedev/i386/RPMS/smeserver-zarafa-0.9.0-53.el4.sme.noarch.rpm
yum localinstall smeserver-zarafa-0.9.0-53.el4.sme.noarch.rpm
/etc/e-smith/events/actions/zarafa-install
expand the php-mapi patch patch and and the symbolic links (see first text block above: Zarafa7 on SME8).
If you use webaccess mobile, change 86ZarafaAlias template [[bugzilla:6552]]
If you use z-push, download and install (see [[Zarafa | here]] mobile synchronization).
You have to change the name of the installation folder from z-push<version #> to z-push, because this is expected by the smeserver-zarafa package.
The download extracts correctly but leaves the file and group ownership to some unknown user 33. I changed that (might not be necessary, I consider it a small security risk).
chown -R root:root /var/www/html/z-push
Then post-upgrade and restart.
For upgrades (tested with 6.40.2): zarafa-server does not start, there is an error message in the /var/log/zarafa/zarafa-server.log file which tells you to update the database first. A python script is provided to do just that. See also [[http://doc.zarafa.com/7.0/Administrator_Manual/en-US/html/upgrading.html zarafa administration manual]]!
Stop running zarafa services, make sure a backup of the zarafa mysql database exists, install MySQL-python, run update script.
yum install MySQL-python
python /usr/share/doc/zarafa/zarafa7-upgrade
Reports the script failes with wrong inno_db settings for mysql are on the zarafa forums. So verify your local MySQL innodb settings match the required values [[http://doc.zarafa.com/7.0/Administrator_Manual/en-US/html/_memory_usage_setup.html zarafa administration manual]]).
===Sogo===
FYI, I'm now using [[Sogo]] instead of zarafa, hence I have stopped work on smeserver-zarafa.
Sogo may not be as complete as zarafa, but is simpler to intergrate/maintain and will likely have a wider usage.
[[User:Snoble|Snoble]] 01:59, 14 March 2010 (UTC)
I will mantain it for now, Paul Floor
=== Suggestions===
=== Suggestions===
If you can advise on standard configuration, please make it a bug so it is added to the rpm
If you can advise on standard configuration, please make it a bug so it is added to the rpm
=== smeserver-zarafa-0.9-47===
=== smeserver-zarafa-0.9-48===
/etc/e-smith/events/actions/zarafa-services-stop has been removed
/etc/e-smith/events/actions/zarafa-services-stop has been removed
=== Upgrade to Zarafa 6.30 ===
InnoDB support is enabled automatically, we need to add this note later
The new Zarafa 6.30 version has some [http://download.zarafa.com/zarafa/drupal/ondemand.php?version=6.30.0&document=Zarafa_Upgrade_Manual&lang=en interesting new features] with the most interesting one CALDAV support.
{{Note box| InnoDB support in MySql has been enabled in order to get zarafa-server running, for details see [[MySQL#Enable_InnoDB_engine]]}}
=== zarafa-6.40 ===
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-*.rpm catdoc-*.rpm
==== indexing service ====
The catdoc-rpm is needed for the new [http://www.zarafa.com/news/26-jan-zarafa-releases-community-version-its-collaboration-platform-640 indexing service] that is introduced with Zarafa 6.40... but the indexing-service is not yet handled by smeserver-zarafa. --[[User:Jester|jester]] 15:42, 13 February 2010 (UTC)
the catdoc rpm has un meet dependencies on SME 7 so it's only listed on discussion not the main page,
yes it's not implemented yet, it'll only be implemented in sme8 unless others find the dependencies
[[User:Snoble|Snoble]] 01:13, 20 February 2010 (UTC)
Dependencies are poppler and poppler-utils. Available here:
ftp://ftp.pbone.net/mirror/apt.kde-redhat.org/kde-redhat/redhat/4/i386/RPMS.stable/poppler-0.5.4-0.3.el4.i386.rpm
ftp://ftp.pbone.net/mirror/apt.kde-redhat.org/kde-redhat/redhat/4/i386/RPMS.stable/poppler-utils-0.5.4-0.3.el4.i386.rpm
NOTE: Some poppler versions have been identified with security issues. I didn't have time to look into this version.
Paul Floor.
=== SME 8 beta ===
==== php 5.2.10 ====
The php mapi files zarafa uses are compiled against 5.1.6, if sme 8 uses 5.2.10 we have a problem
here is one workaround http://forums.zarafa.com/viewtopic.php?f=9&t=3263&p=18753#p18753
I found with the mapi error that I was getting was caused by my upgrade, PHP wouldn't start as the file libvmime.so.0 was missing or something rather (log no longer has the message). How I fixed my issue was I deleted the symlink in the /usr/lib/libvmime.so.0 which pointed to ...libvmime.0.7.1.so which is deleted when you upgrade the packages for version 7. I then "reinstalled" libvmime-0.9.2+... and restarted the httpd damaen and all was right with the world. -- girkers
To finish things off:
==== php 5.3 ====
If you update your system against the testing repo, it will update php to version 5.3 and thus break things again. To fix the mapi error this time, I uninstalled php-mapi that was included with zarafa (I was using 7.0.1.28479 that was included with zarafa) and this also removes the two dependencies of zarafa-webaccess and zarafa-webaccess-mobile (if they are installed). I then downloaded an updated php-mapi, installed it and then reinstalled the webaccess rpms and restarted the httpd and all good again. - Girkers
The steps I did were:
cd /tmp
wget ftp://ftp.pbone.net/mirror/download.fedora.redhat.com/pub/fedora/epel/5/i386/php53-mapi-7.0.1-1.el5.i386.rpm
yum erase php-mapi
yum localinstall php53-mapi-7.0.1-1.el5.i386.rpm
cd zcp-[your version of zarafa]
yum localinstall zarafa-webaccess-*
sv t httpd-e-smith