2.5 Configuring the Ksplice Enhanced Client for Offline Mode

The offline version of the Ksplice Enhanced client removes the requirement that a server on your intranet have a direct connection to the Oracle Uptrack server or to ULN.

At regular intervals, you can download the latest Ksplice update packages to this server. After installing the offline Ksplice Enhanced client on your local systems, they can then connect to the local ULN mirror to receive updates. After you have set up a local ULN mirror to act as a Ksplice mirror, you can then configure your other systems to receive yum updates, as well as Ksplice updates. See Section 1.3.4, “Configuring a Local ULN Mirror to Act as a Ksplice Mirror” for more information about configuring a local ULN mirror.

Configure a system as an offline Ksplice Enhanced client as follows:

  1. Import the GPG key.

    # rpm --import /usr/share/rhn/RPM-GPG-KEY
  2. Disable any existing yum repositories configured in the /etc/yum.repos.d directory. You can either edit any existing repository files and disable all entries by setting enabled=0 or you can use yum-config-manager, for example:

    # yum-config-manager --disable \*

    Alternatively, you can rename any of the files in this directory so that they do not use the .repo suffix. This change causes the yum command to ignore these entries, as shown in the following example:

    # cd /etc/yum.repos.d
    # for i in *.repo; do mv $i $i.disabled; done
  3. In the /etc/yum.repos.d directory, create the local-yum.repo file, which contains entries such as the following for an Oracle Linux 7 yum client:

    name=Ksplice for Oracle Linux $releasever - $basearch
    name=Ksplice aware userspace packages for Oracle Linux $releasever - $basearch
    name=Oracle Linux $releasever - $basearch - latest
    name=Unbreakable Enterprise Kernel Release 5 for Oracle Linux $releasever - $basearch - latest
    name=Oracle Linux $releasever - $basearch - addons
    • Replace local_uln_mirror with the IP address or resolvable host name of the local ULN mirror.

    • To distinguish the local repositories from the ULN repositories, optionally prefix the labels for each entry with a string such as local_. Note that you must also edit the uptrack configuration, as described in step 7.

    • The previous example configuration enables the local_ol7_x86_64_ksplice, local_ol7_x86_64_ksplice_userspace, local_ol7_latest, local_ol7_UEKR5_latest, and local_ol7_addons channels.

  4. Test the configuration:

    1. Clear the yum metadata cache.

      # yum clean metadata
    2. Verify the configuration.

      # yum repolist

      If the yum commands cannot connect to the local ULN mirror, check that the firewall settings on the local ULN mirror server allow incoming TCP connections to the HTTP port (usually, port 80).

  5. If prelink is installed, revert all of the prelinked binaries and dependent libraries to the original states and then remove the prelink package as follows:

    # prelink -au
    # yum remove prelink

    The prelink package is installed and enabled by default on Oracle Linux 6, but not on Oracle Linux 7 or Oracle Linux 8.

  6. Install the offline version of the enhanced client package.

    # yum install ksplice-offline
  7. Add a configuration directive to the /etc/uptrack/uptrack.conf file to provide the enhanced client with the label of the local, user-space channel in your local yum repository configuration.


    You can skip this step if you did not use the local_ prefix for the channel label, and this label is an exact match of the label that is used on ULN. If you used the local_ prefix or labeled this channel differently, add the following lines, but instead of local_ol7_x86_64_ksplice_userspace, specify the same label that you used for the Ksplice Userspace channel, for example:

    yum_userspace_ksplice_repo_name = local_ol7_x86_64_ksplice_userspace
  8. To install offline update packages, install the relevant packages, for example:

    # yum install ksplice-updates-glibc ksplice-updates-openssl

    If you are installing the offline updates package for the Xen hypervisor, specify the release in the command, for example:

    # yum install ksplice-updates-xen-$RELEASE

    For the previous command, $RELEASE is the update package that corresponds to the version of the hypervisor that is currently running, as shown in this example:

    # yum install ksplice-updates-xen-4.4.4-153.el6

    After you have installed these packages, the offline version of the enhanced client behaves exactly the same way as the online version.

  9. Update the system to install the Ksplice-aware versions of the user-space libraries:

    # yum update

    To install just the libraries and not any other packages, limit the update to the Ksplice userspace channel, for example, ol7_x86_64_userspace_ksplice channel:

    # yum --disablerepo=* --enablerepo=ol7_x86_64_userspace_ksplice update

    Alternatively, you can use the following command:

    # yum update *glibc *openssl*

    You might also use this client to perform kernel updates in the same way that you are able to use the standard uptrack client:

    # yum install uptrack-updates-`uname -r`
  10. To enable the automatic installation of updates, change the entry in /etc/uptrack/uptrack.conf from no to yes, as shown in the following example:

    autoinstall = yes
  11. Reboot the system so that the system uses the new libraries.


    If you installed updates for the Xen hypervisor, no special configuration is required, and you do not need to reboot the system for the updates to be applied.