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

You need to configure the OXReportClient.

Please note: The update to v6.22 is only supported from an installed version 6.20.7 or later. If you have an earlier version of Open-Xchange Server 6 installed, please update to the latest release of v6.20 before attempting an update to v6.22.

Updating Open-Xchange Server Packages 6.20.x

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

Add the following entry to /etc/apt/sources.list.d/open-xchange.list

deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/backend/DebianJessie/ /
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/frontend/DebianJessie/ /

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

RHEL6/CentOS6

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/backend/RHEL6/
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/frontend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

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.

RHEL7/CentOS7

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/backend/RHEL7/
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/frontend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

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.

Updating Open-Xchange Server Packages 6.22.x

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

Add the following entry to /etc/apt/sources.list.d/open-xchange.list

deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/DebianJessie/ /
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/frontend/DebianJessie/ /

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 server process needs a restart:

$ /etc/init.d/open-xchange 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

RHEL6/CentOS6

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

[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/frontend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

and run

$ yum update

$ yum upgrade

After the new packages are installed, the server process needs a restart:

$ /etc/init.d/open-xchange 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.

RHEL7/CentOS7

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

[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/frontend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

and run

$ yum update

$ yum upgrade

After the new packages are installed, the server process needs a restart:

$ /etc/init.d/open-xchange 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.

Updating older supported versions of Open-Xchange Server Packages 6.22.x

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

If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to /etc/apt/sources.list.d/open-xchange.list. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See AppSuite:Version_Support_Commitment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the 6.22/stable symlink.)

deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/DebianJessie/ /
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/DebianJessie/ /

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 server process needs a restart:

$ /etc/init.d/open-xchange 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

RHEL6/CentOS6

If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to /etc/yum.repos.d/ox.repo. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See AppSuite:Version_Support_Committment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the 6.22/stable symlink.)

[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

and run

$ yum update

$ yum upgrade

After the new packages are installed, the server process needs a restart:

$ /etc/init.d/open-xchange 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.

RHEL7/CentOS7

If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to /etc/yum.repos.d/ox.repo. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See AppSuite:Version_Support_Committment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the 6.22/stable symlink.)

[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

and run

$ yum update

$ yum upgrade

After the new packages are installed, the server process needs a restart:

$ /etc/init.d/open-xchange 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.

SLES12

If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entries to the repository list. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See AppSuite:Version_Support_Committment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the 6.22/stable symlink.)

$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/SLE_12/ UPDATESBACKEND
$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/SLE_12/ UPDATESFRONTEND

and run

$ zypper dup -r UPDATESBACKEND
$ zypper dup -r UPDATESFRONTEND

You might need to run

$ zypper ref

to update the repository metadata before running zypper up.

After the new packages are installed, the server process needs a restart:

$ /etc/init.d/open-xchange 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.