12.2. Performing Critical Updates to the Server

Red Hat releases critical updates to Red Hat Satellite in the form of an Erratum.
For Red Hat Satellite systems connected to the Internet, apply these errata updates using the Red Hat Update Agent with Red Hat Network. Since the Red Hat Satellite is subscribed to Red Hat Network during initial installation, run the yum update on the Red Hat Satellite or use the website at https://access.redhat.com to apply the updates.

Important

Apache RPMs do not restart the httpd service upon installation. Conducting a full update of the Red Hat Satellite Server (such as with the command yum update) might cause Apache to fail. To avoid this, make sure to restart the httpd service after upgrading it.
Use the following procedure to perform a package update within the same version of Satellite:

Procedure 12.1. Performing Critical Updates to the Server

  1. Stop the satellite services. Keep the database running during the upgrade with
    # rhn-satellite stop --exclude postgresql
    
  2. Take a backup of the satellite's database in a working state. Run the following command and replace the [FILENAME] option with the full path to the backup file that you want to create. This location needs to be writable by the PostgreSQL user:
    # db-control online-backup FILENAME
    
  3. Apply the updates:
    # yum update
    
    Apply all Satellite updates. Updating the schema without updating the rest of the Satellite components can cause issues with the Satellite database.
  4. Update the database schema using spacewalk-schema-upgrade command.
    # spacewalk-schema-upgrade
    
    This process will update your database schema to latest version. The spacewalk-schema-upgrade command will inform you with the results of the upgrade and exact locations of schema upgrade log files. To double-check if the schema update passed, run the following commands:
    # rpm -q satellite-schema
    # rhn-schema-version
    
    If the outputed versions match, continue with the process. Otherwise restore the database with db-control restore /path/to/backup.
  5. Restart Red Hat Satellite:
    # rhn-satellite start --exclude postgresql
    
  6. Clear the search index:
    # service rhn-search cleanindex
    
    It is recommended to clean the search index. The above command triggers the creation of a new one, which in most cases completes within thirty minutes to an hour. You might experience issues with the search features of Satellite 5 if you do not clean the index.
For Red Hat Satellite systems not connected to the Internet, retrieve the packages using a customer account at https://access.redhat.com. Then, apply these packages manually according to instructions in the Errata Advisory.

Warning

It is very important to read the Errata Advisory before applying any Red Hat Satellite Errata Updates. Some Errata Advisories require additional configuration steps to apply certain Red Hat Satellite updates, especially updates to the database. In such cases, the Advisory contains specific and detailed information about necessary steps required.