Red Hat NETWORK SATELLITE SERVER 4.0 Installation Manual

Hide thumbs

Table Of Contents

Table of Contents

Quick Links

Download this manual

RHN Satellite Server 4.0

Installation Guide

Table of Contents

Summary of Contents for Red Hat NETWORK SATELLITE SERVER 4.0

Page 1 RHN Satellite Server 4.0 Installation Guide...
Page 2 All other trademarks referenced herein are the property of their respective owners. The GPG ﬁngerprint 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 3: Table Of Contents
Table of Contents 1. Introduction ........................1 1.1. Red Hat Network ....................1 1.2. RHN Satellite Server..................2 1.3. Terms to Understand ..................2 1.4. How it Works ....................3 1.5. Summary of Steps .....................5 2. Requirements........................9 2.1. Software Requirements ..................9 2.1.1. Red Hat Enterprise Linux AS 4 Packages .........9 2.1.2.
Page 4 7. Troubleshooting......................51 7.1. Log Files ......................51 7.2. General Problems....................52 7.3. Host Not Found/Could Not Determine FQDN ..........53 7.4. Connection Errors ...................54 7.5. Satellite Debugging by Red Hat ..............55 8. Maintenance .........................57 8.1. Managing the Satellite Service ...............57 8.2. Updating the Satellite ..................57 8.3.
Page 5: 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 ﬂexibility and power in keeping servers secure and updated.
Page 6: Rhn Satellite Server
Chapter 1. Introduction Scheduled Actions — use the website to schedule actions, including Errata Updates, • package installs, and software proﬁle updates. Simpliﬁcation — maintaining Red Hat systems becomes a simple, automated process. • 1.2. RHN Satellite Server RHN Satellite Server allows organizations to utilize the beneﬁts of Red Hat Network with- out having to provide public Internet access to their servers or other client systems.
Page 7: How It Works
Chapter 1. Introduction a speciﬁc architecture and Red Hat release. A child channel is a channel associated with a base channel that contains extra packages. Organization Administrator — An Organization Administrator is a user role with the • highest level of control over an organization’s Red Hat Network account. Members of this role can add other users, systems, and system groups to the organization as well as remove them.
Page 8 Chapter 1. Introduction RPM importing tools • Channel maintenance tools (Web-based) • 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 reconﬁgured to retrieve up- dates from the organization’s internal RHN Satellite Server instead of the central Red Hat Network Servers.
Page 9: Summary Of Steps
Chapter 1. Introduction Figure 1-1. Using RHN Satellite Server and RHN Proxy Server Together 1.5. Summary of Steps Implementing a fully functional RHN Satellite Server requires more than installing soft- ware and a database. Client systems must be conﬁgured to use the Satellite. Custom pack- ages and channels should be created for optimal use.
Page 10 3. Your Red Hat contact creates a Satellite-entitled account on the RHN website and sends you 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 4.0. These can be found within the Downloads tab of the respective Channel Details pages.
Page 11 Chapter 1. Introduction and packages. Once the custom RPMs are developed, you can import them into the Satellite using RHN Push and add custom channels in which to store them through the Satellite’s website. Refer to the RHN Channel Management Guide for details.
Page 12 Chapter 1. Introduction...
Page 13: Requirements
Chapter 2. Requirements These requirements must be met before installation. 2.1. Software Requirements To perform an installation, the following software components must be available: Base operating system — RHN Satellite Server is supported with Red Hat Enterprise • Linux AS 3 Update 5 or later, or Red Hat Enterprise Linux AS 4 only. The operating system can be installed from disc, local ISO image, kickstart, or any of the methods supported by Red Hat, but must contain certain packages not included in a standard installation.
Page 14: Red Hat Enterprise Linux As 3 Update 5 Packages
Chapter 2. Requirements 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/. When installing Red Hat Enterprise Linux AS 4 via CD or ISO image, select the following...
Page 15: Hardware Requirements
Chapter 2. Requirements When installing Red Hat Enterprise Linux AS 3 Update 5 via CD or ISO image, select the following package groups: Web Server • Mail Server • Development Tools • Legacy Software Development • Then after operating system installation, register the system with RHN and use the Red Hat Update Agent to install the outstanding packages with the following command: up2date perl-CGI perl-libwww-perl perl-URI perl-XML-Parser perl-DateManip \ perl-XML-Dumper perl-libxml-enno perl-Parse-Yapp perl-XML-Encoding ntp...
Page 16 Chapter 2. Requirements Stand-Alone Database Embedded Database Recommended - Pentium IV processor, Recommended - Pentium IV processor, 2.4GHz dual processor, 512K cache or 2.4GHz dual processor, 512K cache or equivalent equivalent Required - 2 GB of memory Required - 2 GB of memory Recommended - 4 GB of memory Strongly recommended - 4 GB of memory 3 GB storage for base install of Red Hat...
Page 17: Database Requirements
Chapter 2. Requirements The package repository may be any large storage device easily and securely accessed • by the other components. The space requirements depend on the number of packages that will be stored. Default Red Hat channels contain approximately 3 GB of packages each, and that size grows with each synchronization;...
Page 18: Additional Requirements
Chapter 2. Requirements The Oracle database should have a user assigned to RHN Satellite Server with full DDL and DML access to that user’s default tablespace. The user needs standard connection information for the database at the time of installation. The precise access levels required by the Oracle user are as follows: ALTER SESSION •...
Page 19 Chapter 2. Requirements RHN strongly recommends ﬁrewalling the RHN Satellite Server solution from the In- ternet. However, it must be able to issue outbound connections to rhn.redhat.com, xml- rpc.rhn.redhat.com and satellite.rhn.redhat.com on ports 80 and 443. • Synchronized System Times There is great time sensitivity when connecting to a Web server running SSL (Secure Sockets Layer);...
Page 20 Chapter 2. Requirements Satellite Servers running in completely disconnected environments. This feature instead uses Channel Content ISOs that can be downloaded to a separate system to synchronize the Satellite with the central Red Hat Network Servers. All other RHN Satellite Servers should be synchronized directly over the Internet.
Page 21: Example Topologies
Chapter 3. Example Topologies The RHN Satellite Server can be conﬁgured in multiple ways. Select one method depend- ing 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 •...
Page 22: Multiple Satellite Horizontally Tiered Topology
Chapter 3. Example Topologies Figure 3-1. Single Satellite Topology 3.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 conﬁguration and balancing the load of client requests.
Page 23: Satellite-Proxy Vertically Tiered Topology
Chapter 3. Example Topologies Figure 3-2. Multiple Satellite Horizontally Tiered Topology 3.3. Satellite-Proxy Vertically Tiered Topology An alternative method to balance load is to install RHN Proxy Servers below a RHN Satel- lite Server. These Proxies connect to the Satellite for RPMs from Red Hat Network and custom packages created locally.
Page 24 Chapter 3. Example Topologies Figure 3-3. Satellite-Proxy Vertically Tiered Topology...
Page 25: 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 upgrad- ing to a newer version of RHN Satellite Server, contact your Red Hat representative for assistance.
Page 26 Chapter 4. Installation mkdir /mnt/cdrom/ 4. If you are installing from CD and it is not mounted automatically, mount it using the command: mount /dev/cdrom /mnt/cdrom If you are installing from an ISO, mount the ﬁle from within the directory containing it using the command: mount iso_filename /mnt/cdrom -o loop The rest of the instructions assume it is mounted in...
Page 27 Chapter 4. Installation Figure 4-1. Pre-Installation It will ﬁrst update the system and then install the RHN Satellite Server packages, GPG keys, database, and default conﬁguration. It will then restart key services, such httpd 7. After the system is back up, open a Web browser and go to the fully qualiﬁed domain name (FQDN) of the RHN Satellite Server.
Page 28 Chapter 4. Installation Figure 4-2. Administrator Email Address The Administrator Email Address page requires an email address to receive ad- ministrative correspondence. Ideally, this address serves multiple people in your or- ganization to ensure delivery. Keep in mind, this address receives all mail generated by the Satellite, including potentially large quantities of error-related tracebacks.
Page 29 Chapter 4. Installation Figure 4-3. Database Conﬁguration The Database Conﬁguration page collects information required for the Satellite with Stand-Alone Database to connect to its database. For Satellite with Embedded Database installation, skip to the Database Schema page description. For Satellite with Stand-Alone Database, consult your database administrator for the appropri- ate values.
Page 30 Chapter 4. Installation Figure 4-4. Database Schema No input is required on the Database Schema page other than your consent. Click Continue to populate the database. This too can take a while. The Database Popu- lation page appears to help you track the progress. Figure 4-5.
Page 31 Chapter 4. Installation The Database Population page displays a link when population is complete. Click Conﬁguration to continue. The RHN Conﬁguration page appears. Figure 4-6. RHN Conﬁguration The RHN Conﬁguration page enables you to change the way the Satellite com- municates with Red Hat Network.
Page 32 Chapter 4. Installation When ﬁnished, click my.corporate.gateway.example.com:3128. Continue. The Monitoring Conﬁguration page appears. Figure 4-7. Monitoring Conﬁguration The Monitoring Conﬁguration page captures email routing information used in monitoring. This is required only if you intend to receive alert notiﬁcations from probes.
Page 33 Chapter 4. Installation Figure 4-8. RHN Registration The RHN Registration page enables you to register the Satellite with Red Hat Net- work, allowing it to get updates and software channel package data directly. To reg- ister the Satellite, ensure its system proﬁle name is correct (usually the hostname) and complete the RHN Username and RHN Password ﬁelds with the account in- formation provided by your sales representative or established previously by you.
Page 34 Chapter 4. Installation Figure 4-9. RHN Satellite Entitlement Certiﬁcate The RHN Satellite Entitlement Certiﬁcate page gathers your RHN Entitlement Certiﬁcate either by obtaining its location or collecting its contents. To identify the certiﬁcate’s path, click Browse, navigate to the ﬁle, and select it. To input its contents, open your certiﬁcate in a text editor, copy all lines, and paste them directly into the large text ﬁeld at the bottom.
Page 35 Chapter 4. Installation Figure 4-10. Satellite Synchronization The Satellite Synchronization page allows you to initially populate your Satellite with software channel metadata. This is possible during installation only if you chose to register your Satellite with RHN. To synchronize, select the Perform Satellite Sync checkbox and click Continue.
Page 36 Chapter 4. Installation Figure 4-11. SSL Certiﬁcate The SSL Certiﬁcate page collects information necessary to create the Secure Sock- ets Layer (SSL) certiﬁcate used by the Satellite and its client machines. In addition, you may manage your SSL infrastructure using the RHN SSL Maintenance Tool. Refer to the SSL Certiﬁcates chapter of the RHN Client Conﬁguration Guide for instructions.
Page 37 Chapter 4. Installation tion exists on the backups of login information described in Chapter 2 Requirements. The CA Cert Common Name ﬁeld may already be populated with the name of the host machine. This may need to be altered if you’re using multiple RHN Servers in tandem.
Page 38 Chapter 4. Installation from the central RHN Servers. The required ﬁelds are pre-populated with values derived from previous installation steps. Ensure this information is accurate. Checkboxes offer options for including built-in security SSL and GNU Privacy Guard (GPG) features, both of which are advised. In addition, you may enable remote command acceptance and remote conﬁguration management of the systems to be bootstrapped here.
Page 39 Chapter 4. Installation Figure 4-14. Satellite Restart The Satellite Restart page requires no user input and merely provides a placeholder while the system is rebooted. Once ﬁnished, the browser window is redirected to the Satellite Administrator page.
Page 40 Chapter 4. Installation Figure 4-15. Satellite Administrator The Satellite Administrator page enables you to create the Organization Administrator account on the Satellite. This master account can conduct any task available to all other user levels, as well as create other user accounts. As always, ensure this information exists on the backups of login information described in Chapter 2 Requirements.
Page 41: Sendmail Conﬁguration
Chapter 4. Installation Figure 4-16. Account Created 22. The Account Created page signals the end of the installation and conﬁguration pro- cess. You may now begin to import software packages and reconﬁgure client systems to use the Satellite. Refer to Chapter 6 Importing and Synchronizing and the RHN Client Conﬁguration Guide (available under Help) respectively, for instructions.
Page 42: Mysql Installation
Chapter 4. Installation Next, edit the ﬁle on the mail server and add the following line: /etc/aliases rogerthat01: | /etc/smrsh/ack_enqueuer.pl Next, edit the ﬁle 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...
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; how- ever, for RHN Satellite Server, entitlements are contractually agreed-upon beforehand, and they are set at installation time.
Page 44: Uploading The Rhn Entitlement Certiﬁcate
If your RHN Satellite Server is connected to the Internet, you have the option of uploading your new RHN Entitlement Certiﬁcate 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.
Page 45: Command Line Entitlement Options
Chapter 5. Entitlements 5.3. Managing the RHN Certiﬁcate with RHN Satellite Activate For disconnected Satellites or customers who prefer to work locally, Red Hat provides a command line tool for managing your RHN Entitlement Certiﬁcate and activating the Satellite using that certiﬁcate: RHN Satellite Activate ( rhn-satellite-activate This is included with the Satellite installation as part of the rhns-satellite-tools...
Page 46 Chapter 5. Entitlements 2. Activate the Satellite locally by inserting the RHN Entitlement Certiﬁcate into the local database. 3. Activate the Satellite remotely by inserting the RHN Entitlement Certiﬁcate into the central RHN (remote) database. This is typically accomplished during local activa- tion but may require a second step if you chose the option.
Page 47: Importing And Synchronizing
Chapter 6. Importing and Synchronizing After installing the RHN Satellite Server, you must provide it the packages and channels to be served. This chapter explains how to import that data and keep it up-to-date. 6.1. RHN Satellite Synchronization Tool With the Satellite installation, Red Hat Network provides an application designed specif- ically to import and synchronize data - the RHN Satellite Synchronization Tool.
Page 48: Import/Sync Options
Chapter 6. Importing and Synchronizing steps take place ﬁrst. To initiate an individual step, use the channel-families --step option, like so: satellite-sync --step=rpms 6.1.2. Import/Sync Options the RHN Satellite Synchronization Tool offers many other com- In addition to --step mand line options. To use them, insert the option and the appropriate value after the command when launching import/synchronization.
Page 49 Chapter 6. Importing and Synchronizing Option Description Forcibly process all package data without --force-all-packages conducting a diff. Override the amount of messaging sent to --debug-level=LEVEL_NUMBER log ﬁles and generated on the screen set in , 0-6 (2 is default). /etc/rhn/rhn.conf Email a report of what was --email imported/synchronized to the designated...
Page 50: Importing
Chapter 6. Importing and Synchronizing are available for importing and synchronizing. 6.2. Importing Before distributing packages via RHN Satellite Server, the packages must ﬁrst be uploaded to the Satellite. This section describes the process for importing packages and other channel data.
Page 51: Running The Import
Chapter 6. Importing and Synchronizing Channel Content ISOs are mounted and then copied to a temporary repository directory. Before 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.
Page 52: Synchronizing
Chapter 6. Importing and Synchronizing Note Importing package data can take up to two hours per channel. You may begin 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.
Page 53: Synchronizing Errata And Packages Directly Via Rhn
Chapter 6. Importing and Synchronizing During synchronization over the Internet, the RHN Satellite Synchronization Tool per- forms the following steps: 1. Connects over SSL to central RHN Servers, authenticates itself as an RHN Satel- lite Server, and triggers an export of RHN data — unless a local mount point for RHN-exported data is speciﬁed, in which case no connection is necessary.
Page 54: Synchronizing Errata And Packages Via Local Media
Chapter 6. Importing and Synchronizing 6.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. Refer to Section 6.2.2 Preparing for Import for instruc- tions on downloading the ISOs.
Page 55: 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 56: General Problems
Chapter 7. Troubleshooting Component/Task Log File Location Red Hat Update Agent /var/log/up2date XML-RPC transactions /var/log/rhn/rhn_server_xmlrpc.log Table 7-1. Log Files 7.2. General Problems To begin troubleshooting general problems, examine the log ﬁle or ﬁles related to the component exhibiting failures. A useful exercise is to issue the command for all tail -f log ﬁles and then run...
Page 57: Host Not Found/Could Not Determine Fqdn
If the administrator is not getting email from the RHN Satellite Server, conﬁrm 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 web.default_mail_from and appropriate value in /etc/rhn/rhn.conf...
Page 58: Connection Errors
Chapter 7. Troubleshooting To resolve this problem, identify the contents of the ﬁle. It may look like /etc/hosts this: 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 ﬁle and attempt to re-run the RHN client applications or the Apache HTTP Server.
Page 59: Satellite Debugging By Red Hat
Chapter 7. Troubleshooting The following measures can be used to troubleshoot general connection errors: Attempt to connect to the RHN Satellite Server’s database at the command line using • the correct connection string as found in /etc/rhn/rhn.conf sqlplus username/password@sid Ensure the RHN Satellite Server is using Network Time Protocol (NTP) and set to the •...
Page 60 Chapter 7. Troubleshooting * creating tarball (may take some time): /tmp/satellite-debug.tar.bz2 * removing temporary debug tree Debug dump created, stored in /tmp/satellite-debug.tar.bz2 Deliver the generated tarball to your RHN contact or support channel. Once ﬁnished, email the new ﬁle from the directory to your Red Hat representative /tmp/ for immediate diagnosis.
Page 61: Maintenance
RHN Satellite Server or use the website up2date -u at https://rhn.redhat.com to apply the updates. Important Apache RPMs do not restart the httpd service upon installation. Therefore, after conduct- ing a full update of an RHN Satellite Server (such as with the command up2date -uf Apache may fail.
Page 62: Backing Up The Satellite
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 can be applied manually by the customer according to instructions in the Errata Advisory.
Page 63: Using Rhn Db Control
Since (speciﬁcally /var/satellite/ ) is primarily a duplicate of Red Hat’s RPM /var/satellite/redhat/NULL/ repository, it can be regenerated with . Red Hat recommends the satellite-sync entire tree be backed up. In the case of disconnected satellites, /var/satellite/ must be backed up.
Page 64: Backing Up The Database
Chapter 8. Maintenance Option Description Backs up the database to the directory speciﬁed. backup DIRNAME Examines the contents of a backup directory. examine DIRNAME Returns the timestamp of backup creation and reports on its contents. Increase the RHN Oracle tablespace extend Reports on current usage of database space.
Page 65: Verifying The Backup
Chapter 8. Maintenance db-control backup DIRNAME Backup ﬁles are stored in the directory speciﬁed. Note that this is a cold backup; the database must be stopped before running this command. This process takes several min- utes. The ﬁrst backup is a good indicator of how long subsequent backups will take. Once the backup is complete, return to root user mode and restart the database and related services with these commands in this order: service rhn-database start...
Page 66: Cloning The Satellite With Embedded Db
Chapter 8. Maintenance db-control restore DIRNAME This not only restores the Embedded Database but ﬁrst veriﬁes the contents of the backup directory using md5sums. Once the restoration is complete, return to root user mode and restart the database and related services with these commands in this order: service rhn-database start service taskomatic start service httpd start...
Page 67 Chapter 8. Maintenance Database may be run as active, as well as standby. This is entirely up to your network topology and is independent of the steps listed here. To establish this redundancy, ﬁrst install the primary Satellite normally, except the value speciﬁed in the Common Name ﬁeld for the SSL certiﬁcate must represent your high- availability conﬁguration, rather than the hostname of the individual server.
Page 68: Conducting Satellite-Speciﬁc Tasks
Chapter 8. Maintenance You may use custom scripting or other means to establish automatic start-up/failover of the RHN Task Engine on the secondary Satellite. Regardless, it will need to be started upon failover. 7. Share channel package data (by default located in ) between the /var/satellite Satellites over some type of networked storage device.
Page 69 Chapter 8. Maintenance Figure 8-1. Internal Tools To refresh the view of channels that have been updated but do not yet reﬂect those modiﬁ- cations on the Satellite website, click the Update Errata cache now link on this page. 8.7.1.1. Maintaining the RHN Task Engine The default display shows the status of the RHN Task Engine.
Page 70: Deleting Users
Chapter 8. Maintenance Other service commands can also be used, including , and start stop status 8.7.1.2. Accessing the String Manager The Tools menu also offers a String Manager function. This page allows you to edit footers, headers and other universal information displayed in emails, error messages and elsewhere.
Page 71 Chapter 8. Maintenance A conﬁrmation 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 proﬁle before delet- ing the user from the RHN Satellite Server. Failing to do so causes the delete operation to fail.
Page 72: Automating Synchronization
Chapter 8. Maintenance 8.8. Automating Synchronization Manually synchronizing the RHN Satellite Server repository with Red Hat Network can be a time-intensive task. United States business hours tend to be the peak usage time for Red Hat Network, so synchronization at that time may be slow. For these reasons, Red Hat en- courages you to automate synchronization at other times to better balance load and ensure quick synchronization.
Page 73: Enabling Push To Clients
Chapter 8. Maintenance This assumes the PAM service ﬁle is named rhn-satellite To enable a user to authenticate against PAM, select the checkbox labeled Pluggable Au- thentication Modules (PAM). It is positioned below the password and password conﬁr- mation ﬁelds on the Create User page. As an example, to authenticate against Kerberos one could put the following in /etc/pam.d/rhn-satellite #%PAM-1.0...
Page 74 Chapter 8. Maintenance service osad start Like other services, accept , and osa-dispatcher osad stop restart status commands, as well. Keep in mind, this feature depends on the client system recognizing the fully qualiﬁed domain name (FQDN) of the Satellite. This name and not the IP address of the server must be used when conﬁguring the Red Hat Update Agent.
Page 75: Sample Rhn Satellite Server Conﬁguration 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 76 Appendix A. Sample RHN Satellite Server Conﬁguration File web.base_acls = RHN::Access web.default_taskmaster_tasks = RHN::Task::SessionCleanup, RHN::Task::ErrataQueue, RHN::Task::ErrataEngine, RHN::Task::DailySummary, RHN::Task::SummaryPopulation, RHN::Task::RHNProc, RHN::Task::PackageCleanup web.rhn_gpg_backend_module = RHN::GPG::OpenPGP web.restrict_mail_domains =...
Page 77: Index
Index Database Schema, 26 db-control options, 59 Symbols db-control use, 59 disable services /etc/nsswitch.conf, 53 /etc/rhn/rhn.conf, 53 ntsysv chkconﬁg, 16 disconnected mode, 29 Administrator Email Address, 24 advantages, 2 Apache, 57 Apache HTTP, 3 embedded database automating Satellite synchronization, 68 default location /rhnsat/, 21 enabling push to clients, 69...
Page 78 Oracle 9i R2, 3 implementing PAM authentication, 68 Organization Administrator, 36 import deﬁnition, 2 channel content osa-dispatcher, 69 process, 47 osad, 69 importing and synchronizing data, 43 importing data, 46 placing Errata in repository, 48 populating the channel, 48 port 443, 14 port 5222, 16 preparing for, 46 port 5269, 16...
Page 79 RHN Satellite Server entitlement, 22 RHN Satellite Synchronization Tool, 29, 43 terms to understand, 2 options, 44 tool use, 64 RHN SSL Maintenance Tool, 32 topologies, 17 RHN Task Engine, 65, 66 multiple satellites horizontally tiered, 18 RHN Username, 29 satellite and proxies vertically tiered, 19 rhn-satellite single satellite, 17...

This manual is also suitable for:

Rhn satellite server 4.0

Red Hat NETWORK SATELLITE SERVER 4.0 Installation Manual

1 Introduction

2 Requirements

3 Example Topologies

4 Installation

5 Entitlements

6 Importing and Synchronizing

7 Troubleshooting

8 Maintenance

Quick Links

Related Manuals for Red Hat NETWORK SATELLITE SERVER 4.0

Summary of Contents for Red Hat NETWORK SATELLITE SERVER 4.0

This manual is also suitable for:

Table of Contents