Talk:Zarafa
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)
I have allready installed Zarafa on my SME and it looks great, but i miss a lot of configuration things in the wiki. I would be able enter them but i also want to ask for permission first.
Upgrade to Zarafa 6.30
The new Zarafa 6.30 version has some interesting new features with the most interesting one CALDAV support.
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) and extract it: http://www.zarafa.com/download-community
tar -zxvf zarafa-6.30-rhel4-i386.tar.gz
Stop the Zarafa server:
/etc/init.d/zarafa-server stop
When updating the packages the base repo needs to be enabled to satisfy a dependency for the sysstat package:
yum localinstall --enablerepo=base zarafa-6*.rpm zarafa-webaccess-6*.rpm zarafa-licensed-6*.rpm libical*.i386.rpm libvmime*.i386.rpm
To regenerate the configuration files:
/etc/e-smith/events/actions/zarafa-update
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)
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
To finish things off:
signal-event post-upgrade ; signal-event reboot
