8.4 Updating the Server

After the server has been registered in the Customer Center, you can apply the patches. The default GNOME desktop indicates when there are updates available to the server. You can update the server from any of the following interfaces.

You could also patch an OES server using Section 8.7, Patching From Behind a Proxy Server.

8.4.1 Updating the Server Using the Command Line

After you have registered the server in the Customer Center, you can update the server by using commands at the command line. The following procedure specifies steps for updating the server with all available patches for OES 2018 SP1.

  1. Log in to the server as root or su to root.

  2. At the command line, enter the following commands.

    1. Refresh all services:

      zypper ref -s

      The list of repositories should include the following update repositories:

      Enabled Repositories

      • OES2018-SP1-Pool

      • OES2018-SP1-Updates

      • OES2018-SP1-SLES12-SP3-pool

      • OES2018-SP1-SLES12-SP3-Updates

      • OES2018-SP1-SLE-Module-Containers-12-SP3-Pool

      • OES2018-SP1-SLE-Module-Containers-12-SP3-Updates

      Optional/Disabled Repositories

      • OES2018-SP1-SLE-Manager-Tools12-Debuginfo-Pool

      • OES2018-SP1-SLE-Manager-Tools12-Debuginfo-Updates

      • OES2018-SP1-SLE-Manager-Tools12-Pool

      • OES2018-SP1-SLE-Manager-Tools12-Updates

      • OES2018-SP1-SLE-Module-Containers12-Debuginfo-Pool

      • OES2018-SP1-SLE-Module-Containers12-Debuginfo-Updates

      • OES2018-SP1-SLE-Module-Public-Cloud12-Debuginfo-Pool

      • OES2018-SP1-SLE-Module-Public-Cloud12-Debuginfo-Updates

      • OES2018-SP1-SLE-Module-Public-Cloud12-Pool

      • OES2018-SP1-SLE-Module-Public-Cloud12-Updates

      • OES2018-SP1-SLE-Module-Toolchain12-Debuginfo-Pool

      • OES2018-SP1-SLE-Module-Toolchain12-Debuginfo-Updates

      • OES2018-SP1-SLE-Module-Toolchain12-Pool

      • OES2018-SP1-SLE-Module-Toolchain12-Updates

      • OES2018-SP1-SLE-Module-Web-Scripting12-Debuginfo-Pool

      • OES2018-SP1-SLE-Module-Web-Scripting12-Debuginfo-Updates

      • OES2018-SP1-SLE-Module-Web-Scripting12-Pool

      • OES2018-SP1-SLE-Module-Web-Scripting12-Updates

      • OES2018-SP1-SLE-SDK-12-SP3-Debuginfo-Pool

      • OES2018-SP1-SLE-SDK-12-SP3-Debuginfo-Updates

      • OES2018-SP1-SLE-SDK-12-SP3-Pool

      • OES2018-SP1-SLE-SDK-12-SP3-Updates

      • OES2018-SP1-SLES12-SP3-Debuginfo-Pool

      • OES2018-SP1-SLES12-SP3-Debuginfo-Updates

    2. See whether updates are available for OES 2018 SP1:

      zypper patch-check --repo catalog1 --repo catalog2

      For example,

      zypper patch-check --repo OES2018-SP1-SLES12-SP3-Updates --repo OES2018-SP1-Updates

    3. Update the server with all available OES 2018 SP1 patches:

      zypper up -t patch -r OES2018-SP1-SLES12-SP3-Updates -r OES2018-SP1-Updates

    4. Repeat Step 2.b and Step 2.c until no more updates are available.

    5. If the patching requires a server reboot, do so when intimated by the system.

      Rebooting the server activates the new kernel if it has been updated and ensures that OES services that need restarting after patching are restarted.

IMPORTANT:Do not use the zypper up command by itself without the -t option to update an OES server. Always use the -t patch option as described in Section 8.4.1, Updating the Server Using the Command Line.

If the -t patch option is omitted, zypper includes SLES packages in the download that can cripple or completely break OES services.

The -t patch option also ensures that patch metadata (including script files, etc.) is downloaded so that SLES can correctly update the system.

For more information on zypper, see SDB:Zypper usage 11.3.

You can also update your server with specific maintenance patches.

  1. Log in to the server as root or su to root.

  2. At the command line, enter the following commands:

    1. To refresh all services, enter:

      zypper ref -s

    2. To check for available updates, enter:

      zypper lu -r OES2018-SP1-SLES12-SP3-Updates -r OES2018-SP1-Updates

    3. To list the patches and their status, enter:

      zypper pch OES2018-SP1-SLES12-SP3-Updates OES2018-SP1-Updates

    4. To view specific patch information, enter:

      zypper patch-info patch_name

      For example:

      zypper patch-info slessp4-sax2

    5. To list all installed patches, enter:

      zypper search -t pch -i

    6. To update the server with specific patches, choose from the following:

      • To install all patches from one or more catalogs of a particular category:

        zypper patch -r catalog1 -r catalog2 -g category_name

        Replace category_name with security, recommended, or optional.

        For example:

        zypper patch -r OES2018-SP1-SLES12-SP3-Updates -r OES2018-SP1-Updates -g security

      • To install one version of a patch without confirmation, enter:

        zypper --non-interactive in -t patch patch_name-version

        For example:

        zypper --non-interactive in -t patch slessp4-sax2-12428

      • To install all versions of a patch, enter:

        zypper in -t patch patch_name*

    7. If the update requires a server reboot, do so when intimated by the system. This ensures that any changes to the kernel are activated, and applicable OES 2018 SP1 services are restarted.