Chapter 6 Configuring Client Systems for Immediate Updates

By default, the rhnsd daemon on a client system connects to the Spacewalk server every four hours and performs any updates or actions that you have scheduled. If you install the OSA daemon, you can apply updates and actions to client systems immediately from the Spacewalk server.

6.1 Enabling the OSA Daemon in a Kickstart Profile by Using the Spacewalk Web Interface


The following procedure applies if you use Spacewalk to generate the kickstart file.

Configure a kickstart profile to install and enable the OSA daemon on a client system as follows:

  1. Go to Systems, select Kickstart and then Profiles.

  2. Select the profile, and then select Software to display the Package Groups page.

  3. On the Package Groups page, include osad in the list of packages to install.

  4. Select System Details to display the Details page.

  5. On the Details page, select Advanced Options, enable the services option and add the following entry:


    Spacewalk adds the following option to the generated kickstart file:

    services --enabled=osad

    The osad service starts automatically at the default run level when the target client system reboots following installation.

  6. Click Update Kickstart Distribution to save your changes.

6.2 Enabling the OSA Daemon in a Kickstart File


The following procedure applies if you upload a kickstart file into a profile.

If you want to be able to apply updates and actions to a client system immediately from the Spacewalk server:

  • Include the osad package for installation.

  • Include the following kickstart option to enable the osad service:

    services --enabled=osad

6.3 Enabling the OSA Daemon Manually

Install and enable the OSA daemon manually as follows:

  1. Log in as root on the client system.

  2. Use the yum command to install the osad package:

    # yum install osad
  3. Enable and start the osad service:

    • On an Oracle Linux 5 or Oracle Linux 6 client system:

      # chkconfig osad on
      # service osad start
    • On an Oracle Linux 7 client system:

      # systemctl enable osad
      # systemctl start osad
  4. Check that the osa daemon is online.

  5. If the osad service does not start and displays the error SSLDisabledError, edit /etc/sysconfig/rhn/up2date, verify the following for the serverURL entry:

    1. URL uses https://

    2. URL uses the fully qualified domain name of the Spacewalk server or proxy, as shown in the following example:


      If one or both of these settings are not correct, you will need to re-register the client. See Section 5.3, “Registering a Client System by Using rhnreg_ks Without First Installing the Spacewalk Client Software” for instructions.

6.4 Replacing the jabberd/osa Database

You might need to replace the jabberd/osa database on a Spacewalk server or proxy if you encounter any of the following errors:

  • OSA status shows "offline as of unknown" for client servers.

  • osa-dispatcher errors in /var/log/mesasges on the Spacewarlk server or proxy.

  • "db: corruption detected! close all jabberd processes and run db_recover" message in /var/log/messages on the Spacewalk server or proxy.

This problem occurs because the default Berkeley database format does not support transactions, and as a result, can become damaged when too many clients attempt to update at the same time. Switching to SQLite provides transactional support for the jabberd database and can handle significantly more downstream clients.

The workaround for this issue is to replace the database. See Replacing the jabberd/osa Database on Spacewalk Servers or Spacewalk Proxies in Spacewalk for Oracle® Linux: Installation Guide for Release 2.7 for instructions.

6.5 Querying the Status of Client Systems

You can use either the Spacewalk web interface or the spacecmd command to query the status of client systems.

6.5.1 Querying the Status of a Client System by Using the Spacewalk Web Interface

Figure 6.1 System Status Page

To verify the status of an active client system:

  1. Go to Systems and select the client system from the list.

    The Overview page displays the following information for the client system:

    • The System Status pane shows how many critical errata updates, non-critical errata updates, and packages are available to install on the client system. Select Critical, Non-Critical, or Packages to view and optionally install the available errata and packages.

    • The System Info pane shows the host name, IP addresses, kernel version, Spacewalk system ID, activation key, and whether the system is locked.

    • The Subscribed Channels pane shows the base and child channels to which the client system is subscribed.

    • The System Events pane shows when the client system last checked in, when it was registered, when it last booted, and when the OSA daemon last started.

    • The System Properties pane shows the entitlements, notifications, automatic errata update status, system name, summary of the installed operating system, and location.

  2. If the OSA status is shown as online as of unknown, select Ping System.

  3. Wait a few seconds and then reload the page. The status should update and display when the OSA daemon was last started.

6.5.2 Querying the Status of a Client System by Using the spacecmd Command

Verify the status of a client system, use the system_details command as follows:

spacecmd {SSM:0}> system_details
System ID:     1000010000
Locked:        False
Registered:    20170405T13:05:50
Last Checkin:  20170419T06:51:47
OSA Status:    online
Last Boot:     20170405T12:05:04

IP Address:
Kernel:        4.1.12-61.1.33.el7uek.x86_64

Activation Keys

Software Channels
  |-- ol7-x86_64-u4-patch


System Groups