Installation guide

ManualsBrandsRed Hat ManualsComputer equipmentNETWORK SATELLITE SERVER 4.0

Satellite with Stand-Alone Database.

Confirm the correct package:

7 rhn-org-httpd-ssl-key-pair-MACHINE_NAME-VER-REL.no arch.rpm

is ins talled 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 ins tructions.

Make sure client systems are not using firewalls of their own, blocking required ports as

identified in Section 2.4 , “Additional Requirements”.

Wha t do I do if importing or synchronizing a cha nnel fails a nd I can't re cover it ?

If importing/synchronizing a channel fails and you can't recover it in any other way, run this

command to delete the cache:

rm -rf temporary-directory

Note that Section 6.2.2.1, “Preparing Channel Content ISOs” sugges ted that this temporary

directory be /var/rhn-sat-im port/.

Next, restart the importation or synchronization.

I'm ge tt ing "SSL_CO NNECT" errors. What do I do now?

A common connection problem, indicated by SSL_CONNECT errors, is the result of a Satellite being

installed on a machine whose time had been improperly set. During the Satellite installation

process, SSL certificates are created with inaccurate times. If the Satellite's time is then corrected,

the certificate start date and time may be set in the future, making it invalid.

To troubleshoot this, check the date and time on the clients and the Satellite with the following

command:

date

The results should be nearly identical for all machines and within the "notBefore" and "notAfter"

validity windows of the certificates. Check the client certificate dates and times with the following

command:

openssl x509 -dates -noout -in /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

Check the Satellite server certificate dates and times with the following command:

openssl x509 -dates -noout -in /etc/httpd/conf/ssl.crt/server.crt

By default, the s erver 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.

7.4 . Logging a nd Report ing

Wha t a re the differe nt log file s?

Virtually every troubleshooting step should start with a look at the associated log file or files.

These provide invaluable information about the activity that has taken place on the device or within

the application that can be used to monitor performance and ensure proper configuration. See

Table 7.1, “Log Files” for the paths to all relevant log files:

There may be numbered log files (such as /var/log/rhn/rhn_satellite_install.log.1,

/var/log/rhn/rhn_satellite_install.log.2, etc.) within the /var/log/rhn/ directory. These are rotated

logs, which are log files created with a .<NUMBER> extension when the current

rhn_satellite_install.log file fills up to a size as specified by the logrotate(8)

daemon and the contents written to a rotated log file. For example, the

rhn_satellite_install.log.1 contains the oldest rotated log file, while

rhn_satellite_install.log.4 contains the most recently rotated log.

Table 7.1. Log Files

Compone nt /Task Log File Location

Apache Web server /var/log/httpd/ directory

RHN Satellite /var/log/rhn/ directory

RHN Sat ellite Installa tion

Program

/var/log/rhn/rhn_satellite_install.log

Database installation - Embedded

Database

/var/log/rhn/install_db.log

Database population /var/log/rhn/populate_db.log

RHN Sat ellite Synchronization

Tool

/var/log/rhn/rhn_server_satellite.log

Monitoring infrastructure /var/log/nocpulse/ directory

Monitoring notifications /var/log/notification/ directory

RHN DB Cont rol - Embedded

Database

/var/log/rhn/rhn_database.log

RHN Task Engine (taskomatic) /var/log/m essages

yum /var/log/yum .log

XML-RPC transactions /var/log/rhn/rhn_server_xmlrpc.log

How do I use spacewalk-report?

There are instances where administrators may need a concise, formatted summary of their RHN

Satellite resources, whether it is to take inventory of their entitlements, subscribed systems, or

users and organizations. Rather than gathering such information manually from the Satellite Web

interface, RHN Satellite 5.4 includes the spacewalk-report command to gather and display vital

Satellite information at once.

Red Hat Network Satellite 5.4 Installation Guide