5
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 5:
Line 5: + − + − get zcp 7.01, unpack, remove the devel packages and install all rpm's: + + + + + + + + + + + + + + + + + − + Line 28:
Line 45: + + + + + + + + + Line 94:
Line 120: + + + + + + + + + + + + + +
Added information on updating php-mapi if upgraded php to version 5.3
sv t httpd-e-smith
sv t httpd-e-smith
=== Dependancies ===
To make things a bit more easy for non Zarafa experts. I used this procedure for a clean install.
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
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).
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 retrieve this file from the smevdev repository (sme8 uses another one?).
Then install smeserver-zarafa. I could not retrieve this file from the smevdev repository (sme8 uses another one?).
Get it manually and install:
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
wget http://ftp.nluug.nl/os/Linux/distr/smeserver/releases/7/smedev/i386/RPMS/smeserver-zarafa-0.9.0-53.el4.sme.noarch.rpm
Then post-upgrade and restart.
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===
===Sogo===
here is one workaround http://forums.zarafa.com/viewtopic.php?f=9&t=3263&p=18753#p18753
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
==== 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
