Difference between revisions of "Talk:Zarafa"
m |
m |
||
| Line 7: | Line 7: | ||
To make things a bit more easy for non Zarafa experts, I used this procedure for a clean install. | 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). | ||
| Line 28: | Line 28: | ||
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=== | ||
Revision as of 20:22, 30 September 2011
Zarafa7 on SME8
If you want to test the new Zarafa 7 version on SME8b6: install as described 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
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 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 [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 [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.
Snoble 01:59, 14 March 2010 (UTC)
I will mantain it for now, Paul Floor
Suggestions
If you can advise on standard configuration, please make it a bug so it is added to the rpm
Snoble 07:32, 22 December 2008 (UTC)
smeserver-zarafa-0.9-48
/etc/e-smith/events/actions/zarafa-services-stop has been removed
/etc/e-smith/events/actions/zarafa-services Usage: start|stop|restart|enabled|disabled start services stop services restart services enabled - set db values to enabled, zarafa will start on reboot disabled - set db values to disabled, zarafa won't start on reboot
InnoDB support is enabled automatically, we need to add this note later
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 indexing service that is introduced with Zarafa 6.40... but the indexing-service is not yet handled by smeserver-zarafa. --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
Snoble 01:13, 20 February 2010 (UTC)
Dependencies are poppler and poppler-utils. Available here:
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
