Selinux Issues; Updated Software Components; Satellite Debugging By Red Hat - Red Hat NETWORK SATELLITE 5.3.0 Installation Manual

7 rhn-org-httpd-ssl-key-pair-MACHINE_NAME-VER-REL.noarch.rpm
is installed on the RHN Satellite and the corresponding rhn-org-trusted-ssl-cert-
*.noarch.rpm or raw CA SSL public (client) certificate is installed on all client systems.
• Verify the client systems are configured to use the appropriate certificate.
• If also using one or more RHN Proxy Servers, ensure each Proxy's SSL certificates are prepared
correctly. The Proxy should have both its own server SSL key-pair and CA SSL public (client)
certificate installed, since it will serve in both capacities. Refer to the SSL Certificates chapter of the
RHN Client Configuration Guide for specific instructions.
• Make sure client systems are not using firewalls of their own, blocking required ports as identified in
Section 2.4, "Additional

7.5. SELinux Issues

If you encounter any issues with SELinux messages (such as AVC denial messages) on Red Hat
Enterprise Linux 5.1 while installing RHN Satellite, be sure to have the audit.log files available
so that Red Hat Support personnel can assist you. You can find the file in /var/log/audit/
audit.log and can attach the file to your Support ticket for engineers to assist you.

7.6. Updated Software Components

Do not subscribe your RHN Satellite to any of the following child channels available from RHN's
central servers:
• Red Hat Developer Suite
• Red Hat Application Server
• Red Hat Extras
Subscribing to these channels and updating your Satellite (such as by running yum on Red Hat
Enterprise Linux 5 (or up2date on earlier Red Hat Enterprise Linux versions), may install newer,
incompatible versions of critical software components, causing the Satellite to fail.

7.7. 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. The most efficient way to do this is to aggregate your Satellite's configuration parameters, log
files, and database information and send this package directly to Red Hat.
RHN provides a command line tool explicitly for this purpose: The Satellite Diagnostic Info Gatherer,
commonly known by its command satellite-debug. To use this tool, issue the command as root.
You will see the pieces of information collected and the single tarball created, like so:
[root@miab root]# satellite-debug
Collecting and packaging relevant diagnostic information.
Warning: this may take some time...
Requirements".
SELinux Issues
55