1. Manuals
  2. Brands
  3. Red Hat Manuals
  4. Software
  5. NETWORK SATELLITE 5.0.0 -
  6. Installation manual

Red Hat NETWORK SATELLITE 5.0.0 Installation Manual

Hide thumbs Also See for NETWORK SATELLITE 5.0.0:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual
Red Hat Network Satellite
5.0.0
Installation Guide 5.0.0
ISBN: N/A
Publication date:

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the NETWORK SATELLITE 5.0.0 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Red Hat NETWORK SATELLITE 5.0.0

Summary of Contents for Red Hat NETWORK SATELLITE 5.0.0

  • Page 1 Red Hat Network Satellite 5.0.0 Installation Guide 5.0.0 ISBN: N/A Publication date:...
  • Page 2 Red Hat Network Satellite...
  • Page 3 All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the security@redhat.com key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E...
  • Page 4 Red Hat Network Satellite...

  • Page 5: Table Of Contents

    1. Introduction ......................1 1. Red Hat Network ................... 1 2. RHN Satellite Server ..................2 3. Terms to Understand ..................2 4. How it Works ....................3 5. Summary of Steps ..................5 6. Upgrades ...................... 7 2. Requirements ......................9 1.
  • Page 6 Red Hat Network Satellite 5. Updated Software Components ..............57 6. Satellite Debugging by Red Hat ..............58 8. Maintenance ......................59 1. Managing the Satellite Service ...............59 2. Updating the Satellite ..................59 3. Backing Up the Satellite ................60 4. Using RHN DB Control .................61 4.1.

  • Page 7: Introduction

    Chapter 1. Introduction RHN Satellite Server provides a solution to organizations requiring absolute control over and privacy of the maintenance and package deployment of their servers. It allows Red Hat Network customers the greatest flexibility and power in keeping servers secure and updated. Two types of RHN Satellite Server are available: One with a stand-alone database on a separate machine and one with an embedded database installed on the same machine as the Satellite.

  • Page 8: Rhn Satellite Server

    Chapter 1. Introduction 2. RHN Satellite Server RHN Satellite Server allows organizations to utilize the benefits of Red Hat Network without having to provide public Internet access to their servers or other client systems. System Profiles are stored locally on the customer's RHN Satellite Server. The Red Hat Network website is served from a local Web server and is not accessible from the Internet.

  • Page 9: How It Works

    How it Works Red Hat Network organization must have at least one Organization Administrator. • certificate authority — A Channel Administrator is a user role with full access to channel management capabilities. Users with this role are capable of creating channels, assigning packages to channels, cloning channels, and deleting channels.
  • Page 10 Chapter 1. Introduction • Errata management tools (Web-based) • User management tools (Web-based) • Client system and system grouping tools (Web-based) • Red Hat Update Agent on the client systems The Red Hat Update Agent on the client systems must be reconfigured to retrieve updates from the organization's internal RHN Satellite Server instead of the central Red Hat Network Servers.

  • Page 11: Summary Of Steps

    Summary of Steps Figure 1.1. Using RHN Satellite Server and RHN Proxy Server Together 5. Summary of Steps Implementing a fully functional RHN Satellite Server requires more than installing software and a database. Client systems must be configured to use the Satellite. Custom packages and channels should be created for optimal use.
  • Page 12 Chapter 1. Introduction the login information. 4. Log into the RHN website (rhn.redhat.com) and download the distribution ISOs for Red Hat Enterprise Linux AS 3 or 4 and RHN Satellite Server 5.0.0. These can be found within the Downloads tab of the respective Channel Details pages. Refer to the RHN Reference Guide for instructions.

  • Page 13: Upgrades

    The process for upgrading a Satellite from one version to another is not covered within this Satellite Guide, but can be found within the Red Hat Knowledgebase ( http://kbase.redhat.com/faq/ [http://kbase.redhat.com/faq/]) and can be found by performing a search for upgrade satellite or by following this link — http://kbase.redhat.com/faq/FAQ_49_8610.shtm.

  • Page 15: Requirements

    SELINUX=permissive More in-depth coverage of SELinux is available at http://www.redhat.com/docs/. You may also refer to the Red Hat Knowledgebase article on SELinux and RHN Satellite Server at http://kbase.redhat.com/faq/. • Satellite installation disc or ISO — this contains the RHN Satellite Server Installation Program.

  • Page 16: Hardware Requirements

    Chapter 2. Requirements Note Installing packages other than the packages contained in the package @Base group and the package can lead to package conflicts. • Channel content — All software packages and data exported for all entitled Red Hat channels. This content may be loaded directly on the Satellite after installation using the RHN Satellite Synchronization Tool or obtained from your Red Hat representative if synchronization is not possible, such as in a disconnected environment.

  • Page 17: Database Requirements

    Database Requirements Table 2.1. Stand-Alone Database and Embedded Database Satellite Hardware Requirements The following hardware configuration is required for the Stand-Alone Database: • Two processors • 2 GB of memory Section 3, “Database Requirements” for instructions on estimating the tablespace of the database and setting its environment variables.
  • Page 18 Chapter 2. Requirements • 192 KB per client system • 64 MB per channel For instance, an RHN Satellite Server containing 10 channels serving 10,000 systems would require 1.92 GB for its clients and 640 MB for its channels. If custom channels are to be established for testing and staging of packages, they must be included in this formula.

  • Page 19: Additional Requirements

    RHN strongly recommends firewalling the RHN Satellite Server solution from the Internet. However, various TCP ports must be opened on the Satellite, depending on your implementation of RHN Satellite Server: Port Direction Reason Outbound Satellite uses this port to reach rhn.redhat.com [https://rhn.redhat.com], xmlrpc.rhn.redhat.com [http://xmlrpc.rhn.redhat.com] and satellite.rhn.redhat.com...
  • Page 20 Inbound WebUI and client requests come in via either http or https Outbound To reach rhn.redhat.com [https://rhn.redhat.com], xmlrpc.rhn.redhat.com [http://xmlrpc.rhn.redhat.com] and satellite.rhn.redhat.com [http://satellite.rhn.redhat.com](unless running in a disconnected mode for Satellite) 4545 Outbound RHN Satellite Server Monitoring makes connections to...
  • Page 21 It is imperative that customers keep track of all primary login information. For RHN Satellite Server, this includes usernames and passwords for the Organization Administrator account on rhn.redhat.com, the primary administrator account on the Satellite itself, SSL certificate generation, and database connection (which also requires a SID, or net service name). Red...
  • Page 22 Chapter 2. Requirements Hat strongly recommends this information be copied onto two separate floppy disks, printed out on paper, and stored in a fireproof safe. In addition to these requirements, it is recommended that the RHN Satellite Server be configured in the following manner: •...
  • Page 23 Additional Requirements 4. The RHN Reference Guide — This guide describes how to create RHN accounts, register and update systems, and use the RHN website to its utmost potential. This guide will probably come in handy throughout the installation and configuration process.

  • Page 25: Example Topologies

    Chapter 3. Example Topologies The RHN Satellite Server can be configured in multiple ways. Select one method depending on the following factors: • The total number of client systems to be served by the RHN Satellite Server. • The maximum number of clients expected to connect concurrently to the RHN Satellite Server.

  • Page 26: Multiple Satellite Horizontally Tiered Topology

    Chapter 3. Example Topologies 2. Multiple Satellite Horizontally Tiered Topology For very large networks, a more distributed method may be needed, such as having multiple RHN Satellite Servers in a horizontally tiered configuration and balancing the load of client requests. It is possible to synchronize content between RHN Satellites using the commands.
  • Page 27 Satellite-Proxy Vertically Tiered Topology Figure 3.3. Satellite-Proxy Vertically Tiered Topology...

  • Page 29: Installation

    Chapter 4. Installation This chapter describes the initial installation of the RHN Satellite Server. It presumes the prerequisites listed in Chapter 2, Requirements have been met. If you are instead upgrading to a newer version of RHN Satellite Server, contact your Red Hat representative for assistance. 1.
  • Page 30 Chapter 4. Installation mount /dev/cdrom /media/cdrom If you are installing from an ISO, mount the file from within the directory containing it using the command: mount -o loop iso_filename /media/cdrom The remaining instructions assume it is mounted in /media/cdrom/ 4. Ensure that the RHN Entitlement Certificate has been copied onto the Satellite's file system. It can be named anything and located in any directory.
  • Page 31 RHN Satellite Server Installation Program 7. At the prompt, enter the email address to which you would like notifications from the Satellite to be sent. It may be a good idea to choose a general email address rather than the address of an individual, as there can be a large volume of emails.
  • Page 32 Chapter 4. Installation * Activating Satellite. Where is your satellite certificate file? /root/example.cert 13. T he next step is to create a CA cert for the Satellite. To do so, you must answer a few questions. CA cert Enter a password for the certificate. Organization Enter the name of your organization Email Address...
  • Page 33 RHN Satellite Server Installation Program Figure 4.1. Admin Account Creation 16. A blue text box appears at the top of the screen indicating that you can now custom-configure the Satellite and its behavior. To do so, click the bold clicking here text at the end.
  • Page 34 Chapter 4. Installation Figure 4.2. Final Configuration Prompt 17. T he Satellite Configuration - General Configuration page allows you to alter the most basic Satellite settings, such as the admin email address and whether Monitoring is enabled.
  • Page 35 RHN Satellite Server Installation Program Figure 4.3. General Configuration 18. T he RHN Satellite Configuration - Monitoring page allows you to configure the monitoring aspects of this Satellite. The local mail exchanger and local main domain are used to mail monitoring notification messages to administration.
  • Page 36 Chapter 4. Installation Figure 4.4. Monitoring 19. T he RHN Satellite Configuration - Certificate page allows you to upload a new Satellite certificate. To identify the certificate's path, click Browse, navigate to the file, and select it. To input its contents, open your certificate in a text editor, copy all lines, and paste them directly into the large text field at the bottom.
  • Page 37 RHN Satellite Server Installation Program Figure 4.5. Certificate 20. T he RHN Satellite Configuration - Bootstrap page allows you to generate a bootstrap script for redirecting client systems from the central RHN Servers to the Satellite. This script, to be placed in the directory of the Satellite, significantly /var/www/html/pub/bootstrap/ reduces the effort involved in reconfiguring all systems, which by default obtain packages...
  • Page 38 Chapter 4. Installation Figure 4.6. Bootstrap 21. T he RHN Satellite Configuration - Restart page contains the final step in configuring the Satellite. Click the Restart button to restart the Satellite in order to incorporate all of the configuration options added on the previous screens. Note that it will take between four and five minutes for the restart to finish.

  • Page 39: Options To The Satellite Installation Program

    Options to the Satellite Installation Program Figure 4.7. Restart 22. O nce the Satellite has restarted, the countdown notice disappears. You are now free to begin using your Satellite. Figure 4.8. Restart Complete 2.1. Options to the Satellite Installation Program The various options available for the Satellite Installation Program are included below for easy reference.

  • Page 40: Automated Rhn Satellite Server Installation

    Chapter 4. Installation Option Usage Indicates the location of an answer file to be use for --answer-file=<filename> answering questions asked during the installation process. For use only with . If the --non-interactive --answer-file --answer-file does not provide a required response, exit instead of prompting the user.

  • Page 41: Sendmail Configuration

    Sendmail Configuration Follow the steps below to perform an automated install with an answer file: 1. Follow steps 1 through 5 from Section 2, “RHN Satellite Server Installation Program”. 2. Copy the example file to answers.txt /tmp/answers.txt cp answers.txt /tmp/answers.txt 3.

  • Page 42: Mysql Installation

    Chapter 4. Installation rogerthat01: | /etc/smrsh/ack_enqueuer.pl Next, edit the file and change: /etc/mail/sendmail.mc "DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl" "DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnl" Then, have the alias processed like so: newaliases Finally, update the package: sendmail-cf up2date sendmail-cf Note, disconnected installs must obtain this package from the ISO. Restart sendmail: service sendmail restart 5.

  • Page 43: Entitlements

    Chapter 5. Entitlements The RHN Satellite Server, like RHN itself, provides all services to customers through the setting of entitlements. For RHN, entitlements are purchased by customers as needed; however, for RHN Satellite Server, entitlements are contractually agreed-upon beforehand, and they are set at installation time.

  • Page 44: Uploading The Rhn Entitlement Certificate

    If your RHN Satellite Server is connected to the Internet, you have the option of uploading your new RHN Entitlement Certificate through the RHN website. To do this: 1. Log into https://rhn.redhat.com with your organization's Satellite-entitled account. 2. Click Systems in the top navigation bar and then the name of the RHN Satellite Server. You may also find the Satellite through the Satellite line item within the Channels category.

  • Page 45: Command Line Entitlement Options

    Command Line Entitlement Options the Satellite installation as part of the package. rhns-satellite-tools 3.1. Command Line Entitlement Options tool offers a handful of command line options for activating a rhn-satellite-activate Satellite using its RHN Entitlement Certificate: Option Description Display the help screen with a list of options. --help Confirm certificate sanity.

  • Page 46: Satellite Entitlement Certificate Expiration

    Chapter 5. Entitlements To validate an RHN Entitlement Certificate and populate the local database: rhn-satellite-activate --disconnected --rhn-cert=/path/to/demo.cert To validate an RHN Entitlement Certificate and populate both the local and the RHN database: rhn-satellite-activate --rhn-cert=/path/to/demo.cert Once you run this final command, the Satellite is running and able to serve packages locally and synchronize with the central RHN Servers.

  • Page 47: Importing And Synchronizing

    Chapter 6. Importing and Synchronizing After installing the RHN Satellite Server, you must provide it with the packages and channels to be served to client systems. This chapter explains how to import that data and keep it up to date whether the content is from RHN's central servers, local media, or from one Satellite within your organization to another.

  • Page 48: Exporting

    Chapter 6. Importing and Sync... When exporting an RHN base channel, you must also export the tools channel associated with that base channel in order to kickstart machines to the distribution in the base channel. For instance, if you export rhel-i386-as-4 you must also export the rhn-tools-rhel-4-as-i386 channel in order to kickstart machines to Red Hat Enterprise Linux 4 AS.

  • Page 49: Importing With Rhn Satellite Synchronization Tool

    Importing with RHN Satellite To perform a RHN Satellite Exporter export, the following prerequisites must be met: • The RHN Satellite Server installation must have been performed successfully. • There must be sufficient disk space in the directory specified in the option to contain --dir the exported contents.
  • Page 50 Chapter 6. Importing and Sync... satellite-sync This tool can be used in a closed environment, such as the one created with a disconnected install, or it may obtain data directly over the Internet. Closed environment imports can get their data from downloaded ISOs or from the XML data generated by RHN Satellite Exporter. The RHN Satellite Synchronization Tool works incrementally, or in steps.
  • Page 51 Synchronization Tool Option Description Process data for this channel only. --channel=CHANNEL_LABEL Multiple channels can be included by repeating the option. If no channels are specified, all channels on the Satellite will be freshened. Print the current configuration and exit. -p, --print-configuration Not Advisable - Turn off SSL.

  • Page 52: Preparing For Import From Local Media

    Chapter 6. Importing and Sync... Option Description For debugging only - Include path to --systemid=SYSTEM_ID alternative digital system ID. For debugging only - Set maximum --batch-size=BATCH_SIZE batch size in percent for XML/database-import processing. Open man satellite-sync for more information. Table 6.2. Satellite Import/Sync Options If no options are included, synchronizes all channels that already exist in the satellite-sync...
  • Page 53 Preparing for Import from Local Media mounting the ISOs, ensure the temporary repository has enough disk space to copy all the contents into a single directory. For a single channel, the approximate required space is 3 GB. The process to copy Channel Content ISOs is to mount each one, copy its contents to the temporary repository, and then unmount the ISO.

  • Page 54: Running The Import

    Chapter 6. Importing and Sync... procede to running the import as described in Section 2.3, “Running the Import”. 1. Log into the machine as root. 2. Create a target directory for the files, such as: mkdir /var/rhn-sat-import/ 3. Make the export data available on the local machine in the directory created in the previous step.

  • Page 55: Synchronizing

    Synchronizing registering systems to channels as soon as they appear in the RHN Satellite Server's website. No packages are necessary for registration, although updates cannot be retrieved from the Satellite until the channel is completely populated. You may repeat this step for each channel or include them all within a single command by passing each channel label preceded by an additional flag, like so: satellite-sync -c channel-label-1 \...

  • Page 56: Synchronizing Errata And Packages Directly Via Rhn

    Chapter 6. Importing and Sync... the RHN Satellite Server is designed to be a standalone environment, any update advisories published by RHN must be manually imported and synchronized by the administrator of the RHN Satellite Server. During synchronization over the Internet, the RHN Satellite Synchronization Tool performs the following steps: 1.

  • Page 57: Synchronizing Errata And Packages Via Local Media

    Synchronizing Errata and Packages via Multiple channels can be included by repeating the option. If no channels are specified, all channels on the Satellite will be refreshed. 3.2. Synchronizing Errata and Packages via Local Media For customers who cannot connect their Satellite directly to RHN, Red Hat recommends downloading Channel Content ISOs to a separate, Internet-connected system and then transferring them to the Satellite.

  • Page 59: Troubleshooting

    This chapter provides tips for determining the cause of and resolving the most common errors associated with RHN Satellite Server. If you need additional help, contact Red Hat Network support at https://rhn.redhat.com/help/contact.pxt. Log in using your Satellite-entitled account to see your full list of options.
  • Page 60 Chapter 7. Troubleshooting component exhibiting failures. A useful exercise is to issue the command for all log tail -f files and then run . You should then examine all new log entries for potential up2date --list clues. A common issue is full disk space. An almost sure sign of this is the appearance of halted writing in the log files.

  • Page 61: Host Not Found/Could Not Determine Fqdn

    If the administrator is not getting email from the RHN Satellite Server, confirm the correct email addresses have been set for traceback_mail /etc/rhn/rhn.conf If the traceback mail is marked from dev-null@rhn.redhat.com and you would like the address to be valid for your organization, include the option and appropriate web.default_mail_from value in /etc/rhn/rhn.conf...

  • Page 62: Connection Errors

    Chapter 7. Troubleshooting and the RHN client applications to work. To resolve this problem, identify the contents of the file. It may look like this: /etc/hosts 127.0.0.1 this_machine.example.com this_machine localhost.localdomain \ localhost First, in a text editor, remove the offending machine information, like so: 127.0.0.1 localhost.localdomain.com localhost Then, save the file and attempt to re-run the RHN client applications or the Apache Web server.

  • Page 63: Updated Software Components

    Updated Software Components By default, the server certificate has a one-year life while client certificates are good for 10 years. If you find the certificates are incorrect, you can either wait for the valid start time, if possible, or create new certificates, preferably with all system times set to GMT. The following measures can be used to troubleshoot general connection errors: •...

  • Page 64: Satellite Debugging By Red Hat

    Chapter 7. Troubleshooting Subscribing to these channels and updating your Satellite (such as by running ), may up2date install newer, incompatible versions of critical software components, causing the Satellite to fail. 6. Satellite Debugging by Red Hat If you've exhausted these troubleshooting steps or want to defer them to Red Hat Network professionals, Red Hat recommends you take advantage of the strong support that comes with RHN Satellite Server.

  • Page 65: Maintenance

    ), Apache may fail. To avoid this, make sure you restart the httpd up2date -uf service after upgrading it. For RHN Satellite Server systems that may not be connected to the Internet, the packages themselves may be retrieved using a customer account at https://rhn.redhat.com. Then, they...

  • Page 66: Backing Up The Satellite

    /etc/sysconfig/rhn/ • /etc/rhn/ • /etc/tnsnames.ora • /var/www/html/pub/ • - custom RPMs /var/satellite/redhat/1 • - pertains only to RHN Satellite Server 1.1.x. /etc/pxtdb.conf • /root/ssl-build/ If possible, back up , as well. In case of failure, this will save lengthy /var/satellite/ download time.

  • Page 67: Using Rhn Db Control

    Using RHN DB Control Backing up only these files and directories would require reinstalling the RHN Satellite Server ISO RPMs and reregistering the Satellite. In addition, Red Hat packages would need to be resynchronized using the tool. Finally, you would have to reinstall the satellite-sync /root/ssl-build/\ rhn-org-httpd-ssl-key-pair-MACHINE_NAME-VER-REL.noarch.rpm Another method would be to back up all of the files and directories mentioned above but...

  • Page 68: Backing Up The Database

    Chapter 8. Maintenance Option Description DIRNAME. Database must be stopped for this command to run successfully. Starts the database instance. This can also be start accomplished by issuing the service command as root. rhn-database start Shows the current status of the database, either status "running"...

  • Page 69: Verifying The Backup

    Verifying the Backup You should then copy that backup to another system using rsync or another file-transfer utility. Red Hat strongly recommends scheduling the backup process automatically using cron jobs. For instance, back up the system at 3 a.m. and then copy the backup to the separate repository (partition, disk, or system) at 6 a.m.

  • Page 70: Cloning The Satellite With Embedded Db

    Chapter 8. Maintenance 5. Cloning the Satellite with Embedded DB You may limit outages caused by hardware or other failures by cloning the Satellite with Embedded Database in its entirety. The secondary Satellite machine can be prepared for use if the primary fails.

  • Page 71: Conducting Satellite-Specific Tasks

    Conducting Satellite-Specific Tasks register the new Satellite. If your original SSL certificate does not take your high-availability solution into account, you may create a new one with a more appropriate Common Name value now. In this case, you may also generate a new bootstrap script that captures this new value. 3.

  • Page 72: Using The Tools Menu

    Chapter 8. Maintenance standard tasks, such as editing System Profiles and updating packages. Tasks directly related to managing custom channels and Errata are covered in the RHN Channel Management Guide. This section seeks to explain activities available only to Satellite customers. 7.1.

  • Page 73: Deleting Users

    Deleting Users times for various activities carried out by the daemon. Administrators should ensure the RHN Task Engine stays up and running. If this daemon hangs for any reason, it can be restarted using it's filename, . As root, run the taskomatic command: /sbin/service taskomatic restart...

  • Page 74: Automating Synchronization

    Chapter 8. Maintenance A confirmation page appears explaining that this removal is permanent. To continue, click Delete User at the bottom-right corner of the page. Note The Organization Administrator role must be removed from the user's profile before deleting the user from the RHN Satellite Server. Failing to do so causes the delete operation to fail.

  • Page 75: Implementing Pam Authentication

    Implementing PAM Authentication synchronization. Continental United States business hours are roughly 8:00 AM to 9:00 PM EST (UTC -5), due to four time zones, Monday through Friday. These hours may vary seasonally by one hour. Further, Red Hat strongly recommends that synchronization occur randomly for best performance.

  • Page 76: Enabling Push To Clients

    Chapter 8. Maintenance Set up a PAM service file (usually ) and have the Satellite use it by /etc/pam.d/rhn-satellite adding the following line to /etc/rhn/rhn.conf pam_auth_service = rhn-satellite This assumes the PAM service file is named rhn-satellite To enable a user to authenticate against PAM, select the checkbox labeled Pluggable Authentication Modules (PAM).
  • Page 77 Enabling Push to Clients service osa-dispatcher start Finally, install the package on all client systems to receive pushed actions. The package osad can be found within the RHN Tools child channel for the systems on the RHN Satellite Server. Once installed, start the service on the client systems as root using the command: service osad start Like other services, accept...

  • Page 79: Sample Rhn Satellite Server Configuration File

    #/etc/rhn/rhn.conf example for an RHN Satellite #---------------------------------------------- # Destination of all tracebacks, such as crash information, etc. traceback_mail = test@pobox.com, test@redhat.com # Location of RPMs (Red Hat and custom) served by the RHN Satellite mount_point = /var/satellite # Corporate gateway (hostname:PORT): server.satellite.http_proxy = corporate_gateway.example.com:8080...
  • Page 80 Appendix A. Sample RHN Satell... RHN::Task::RHNProc, RHN::Task::PackageCleanup web.rhn_gpg_backend_module = RHN::GPG::OpenPGP web.restrict_mail_domains =...

  • Page 81: Index

    chkconfig, 16 Index embedded database Symbols default location /rhnsat/, 23 /etc/nsswitch.conf, 55 enabling push to clients, 70 /etc/rhn/rhn.conf, 55 entitlement certificate, 15, 23 uploading, 38 advantages, 2 Apache, 59 firewall rules Apache HTTP, 3 requirements, 13 automating Satellite synchronization, 68 general problems, 53 backing up the RHN Satellite Server, 60 GPG keys, 23...
  • Page 82 Index components, 3 RHN DB Control maintenance, 59 backup, 62 mysql-server, 36 options, 61 restore, 63 verify, 63 Network Time Protocol, 14 RHN Entitlement Certificate ntp, 14 options, 39 ntsysv, 16 RHN Entitlement Certificates, 37 receiving, 37 RHN Satellite Activate, 38 operating system RHN Satellite Exporter, 41 supported, 9...
  • Page 83 terms to understand, 2 tool use, 65 topologies, 19 multiple satellites horizontally tiered, 20 satellite and proxies vertically tiered, 20 single satellite, 19 traceback, 3 definition, 2 troubleshooting, 53 /etc/hosts, 54 Embedded Database, 54 full disk space, 54 SSL_CONNECT errors, 56 traceback email address, 55 updating the RHN Satellite Server, 59...

Table of Contents