OX6:UpdatingOXPackages: Difference between revisions

From Open-Xchange
No edit summary
 
(25 intermediate revisions by 4 users not shown)
Line 10: Line 10:
* OX HE
* OX HE


Have a look at the article:
You need to configure the [[OXReportClient]].
[http://sdb.open-xchange.com/node/65 How to create an OXAccount and unlock Keys within the License Database]
for more information about how to create an account in the [http://ldb.open-xchange.com LDB].


In addition, 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 ==
= Updating Open-Xchange Server Packages 6.20.x =


=== Installing Updates ===
== 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.
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 ====
=== 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 <tt>postinst</tt> 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.
Add the following entry to <tt>/etc/apt/sources.list.d/open-xchange.list</tt>


You can do that in answering all the questions like e.g. this
  deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/backend/DebianJessie/ /
 
  deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/frontend/DebianJessie/ /
  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 <tt>diff</tt> on the currently installed configuration and the updated configuration files which are copied to the configuration directory and have the file extension <tt>.dpkg-dist</tt>.
 
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 <tt>/etc/apt/sources.list</tt>
 
  deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/DebianSqueeze/


Then run
Then run
Line 68: Line 39:
{{RestartAfterUpdate}}
{{RestartAfterUpdate}}


==== On RPM based distributions ====
=== On RPM based distributions ===


===== RHEL6/CentOS6 =====
==== RHEL6/CentOS6 ====


Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:
Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:
Line 76: Line 47:
  [ox-updates]
  [ox-updates]
  name=Open-Xchange Updates
  name=Open-Xchange Updates
  baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/RHEL6/
  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
  gpgkey=http://software.open-xchange.com/oxbuildkey.pub
  enabled=1
  enabled=1
Line 91: Line 63:
{{RestartAfterUpdate}}
{{RestartAfterUpdate}}


===== RHEL5/CentOS5 =====
==== RHEL7/CentOS7 ====


Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:
Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:
Line 97: Line 69:
  [ox-updates]
  [ox-updates]
  name=Open-Xchange Updates
  name=Open-Xchange Updates
  baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/RHEL5/
  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
  gpgkey=http://software.open-xchange.com/oxbuildkey.pub
  enabled=1
  enabled=1
Line 112: Line 85:
{{RestartAfterUpdate}}
{{RestartAfterUpdate}}


===== SLES11 =====
= Updating Open-Xchange Server Packages 6.22.x =


Add the updates repository to the repository list:
== Installing Updates ==


$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/SLES11/ OXUPDATES
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.


and run
=== On Debian based distributions ===
 
Add the following entry to <tt>/etc/apt/sources.list.d/open-xchange.list</tt>
 
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
 
{{RestartAfterUpdate|release=6.22}}
 
=== On RPM based distributions ===
 
==== RHEL6/CentOS6 ====


$ zypper dup -r OXUPDATES
Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:


You might need to run
[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


$ zypper ref


to update the repository metadata before running ''zypper up''.
and run


{{RestartAfterUpdate}}
$ yum update


== Updating Open-Xchange Server Packages 6.22 ==
$ yum upgrade


=== Installing Updates ===
{{RestartAfterUpdate|release=6.22}}


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.
==== RHEL7/CentOS7 ====


==== On Debian based distributions ====
Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:


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 <tt>postinst</tt> 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.
[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


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


  Configuration file `/opt/open-xchange/etc/groupware/system.properties'
  $ yum update
  ==> 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".
$ yum upgrade


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 <tt>diff</tt> on the currently installed configuration and the updated configuration files which are copied to the configuration directory and have the file extension <tt>.dpkg-dist</tt>.
{{RestartAfterUpdate|release=6.22}}


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:
= Updating older supported versions of Open-Xchange Server Packages 6.22.x =


cat<<EOF > /etc/apt/apt.conf.d/01oxupdater
== Installing Updates ==
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.
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.
''


Add the following entry to <tt>/etc/apt/sources.list</tt>
=== 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 <tt>/etc/apt/sources.list.d/open-xchange.list</tt>. 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 <tt>6.22/stable</tt> symlink.)


  deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/DebianSqueeze/
  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
Then run
Line 180: Line 191:
  $ apt-get dist-upgrade -s
  $ apt-get dist-upgrade -s


{{RestartAfterUpdate}}
{{RestartAfterUpdate|release=6.22}}


==== On RPM based distributions ====
=== On RPM based distributions ===


===== RHEL6/CentOS6 =====
==== RHEL6/CentOS6 ====


Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:
If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>. 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 <tt>6.22/stable</tt> symlink.)


  [ox-updates]
  [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
  name=Open-Xchange Updates
  baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/RHEL6/
  baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/RHEL6/
  gpgkey=http://software.open-xchange.com/oxbuildkey.pub
  gpgkey=http://software.open-xchange.com/oxbuildkey.pub
  enabled=1
  enabled=1
Line 203: Line 222:
  $ yum upgrade
  $ yum upgrade


{{RestartAfterUpdate}}
{{RestartAfterUpdate|release=6.22}}


===== RHEL5/CentOS5 =====
==== RHEL7/CentOS7 ====


Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:
If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>. 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 <tt>6.22/stable</tt> symlink.)


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


and run
and run
Line 224: Line 250:
  $ yum upgrade
  $ yum upgrade


{{RestartAfterUpdate}}
{{RestartAfterUpdate|release=6.22}}


===== SLES11 =====
==== SLES12 ====


Add the updates repository to the repository list:
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 <tt>6.22/stable</tt> symlink.)


  $ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/SLES11/ OXUPDATES
  $ 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
and run


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


You might need to run
You might need to run
Line 242: Line 271:
to update the repository metadata before running ''zypper up''.
to update the repository metadata before running ''zypper up''.


{{RestartAfterUpdate}}
{{RestartAfterUpdate|release=6.22}}
 




[[Category: OX6]]
[[Category: OX6]]

Latest revision as of 10:31, 21 November 2019

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.

Retrieved from "https://wiki.open-xchange.com/wiki/index.php?title=OX6:UpdatingOXPackages&oldid=25064"