OX6:UpdatingOXPackages

Updating Open-Xchange Server packages

This article describes how to update Open-Xchange Server packages from one service pack to another.

How to get updates?

Open-Xchange Server 6 updates can be accessed by customers with a valid license for

• OX SE
• OX HE

Have a look at the article: How to create an OXAccount and unlock Keys within the License Database for more information about how to create an account in the LDB.

In addition, you need to configure the OXReportClient.

Installing Updates

A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following must be done when installing updates.

On Debian based distributions

To ensure, that all required configuration file changes will be applied to the Open-Xchange packages, you need to leave the original files as they are and the postinst mechanism will automatically apply all new configuration options to the existing configuration files. Existing configuration parameters will not be automatically updated and need to be reviewed manually.

You can do that in answering all the questions like e.g. this

Configuration file `/opt/open-xchange/etc/groupware/system.properties'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : background this process to examine the situation
 The default action is to keep your current version.
*** system.properties (Y/I/N/O/D/Z) [default=N] ?

with the default answer "N".

Note: this will not replace the existing configuration files. Depending on the new Open-Xchange version you're installing it is mandatory that configuration options shipped with the new packages are taken over to the configuration. This can be done by using diff on the currently installed configuration and the updated configuration files which are copied to the configuration directory and have the file extension .dpkg-dist.

If you don't want to do that every time, you could tell apt-get to answer this question for you, just cut and paste the following command in a shell as root user:

cat<<EOF > /etc/apt/apt.conf.d/01oxupdater
DPkg::options {"--force-confold";};
EOF

Note: This change will apply to ALL packages you are going to update in the future, not only Open-Xchange packages.

Add the following entry to /etc/apt/sources.list

deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/DebianLenny /

Then run

$ apt-get update

$ apt-get dist-upgrade

If you want to see, what apt-get is going to do without actually doing it, you can run:

$ apt-get dist-upgrade -s

After the new packages are installed, the groupware and admin process needs a restart:

$ /etc/init.d/open-xchange-groupware restart
$ /etc/init.d/open-xchange-admin restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

On RPM based distributions

RHEL5/RHEL6/CentOS

Add the following entry to /etc/yum.repos.d/ox.repo:

[ox-updates]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/RHEL5/
enabled=1
gpgcheck=0

and run

$ yum update

$ yum upgrade

After the new packages are installed, the groupware and admin process needs a restart:

$ /etc/init.d/open-xchange-groupware restart
$ /etc/init.d/open-xchange-admin restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

SLES10

Add the updates repository to the repository list:

$ zypper sa http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/SLES10/ OXUPDATES

and run

$ zypper up -y -t package

Note: package is not the name of a package, but an option, so just copy and paste the complete line.

After the new packages are installed, the groupware and admin process needs a restart:

$ /etc/init.d/open-xchange-groupware restart
$ /etc/init.d/open-xchange-admin restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

SLES11

Add the updates repository to the repository list:

$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/SLES11/ OXUPDATES

and run

$ zypper dup -r OXUPDATES

You might need to run

$ zypper ref

to update the repository metadata before running zypper up.

After the new packages are installed, the groupware and admin process needs a restart:

$ /etc/init.d/open-xchange-groupware restart
$ /etc/init.d/open-xchange-admin restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.