Difference between revisions of "Talk:Zarafa"

From SME Server
Jump to navigationJump to search
Line 13: Line 13:
 
   signal-event pre-backup
 
   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
+
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
 
   tar -zxvf zarafa-6.30-rhel4-i386.tar.gz
  
 
Stop the Zarafa server:
 
Stop the Zarafa server:
   /etc/init.d/zarafa-server stop
+
   /etc/e-smith/events/actions/zarafa-services-stop
  
When updating the packages the base repo needs to be enabled to satisfy a dependency for the sysstat package:
+
   yum localinstall zarafa-6*.rpm zarafa-webaccess-6*.rpm libical*.i386.rpm libvmime*.i386.rpm zarafa-licensed-6*.rpm (last not required for GPL)
   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:
 
To regenerate the configuration files:
   /etc/e-smith/events/actions/zarafa-update
+
   /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:
 
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:
Line 29: Line 28:
 
   tail -f /var/log/zarafa/server.log
 
   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!
+
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
 
   Start: Adding externid to 'object' table
 
   Done: Adding externid to 'object' table
 
   Done: Adding externid to 'object' table
Line 46: Line 45:
 
To finish things off:
 
To finish things off:
 
   signal-event post-upgrade ; signal-event reboot
 
   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.
 
'''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.
 
====upgrade comments====
 
thanks for posting 
 
see these for a suggested way to start and stop all zarafa services in the correct order (or the way that doesn't gives me errors)
 
/etc/e-smith/events/actions/zarafa-services
 
/etc/e-smith/events/actions/zarafa-services-stop
 
 
note it uses ical, without looking caldev probably needs to be added as a new service, I'll look mid week
 
 
base should already be enabled
 
http://wiki.contribs.org/SME_Server:Documentation:FAQ#Which_repositories_should_be_enabled
 

Revision as of 13:35, 27 July 2009

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 (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

To finish things off:

 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.