2,569
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 13:
Line 13: − + − + − When updating the packages the base repo needs to be enabled to satisfy a dependency for the sysstat package:+ − − + Line 29:
Line 28: − + Line 46:
Line 45: − − − ====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
→Upgrade to Zarafa 6.30
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
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:
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
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.
