Satellite Debugging By Red Hat - Red Hat NETWORK SATELLITE SERVER 4.1.0 Installation Manual

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
sqlplus username/password@sid
Ensure the RHN Satellite Server is using Network Time Protocol (NTP) and set to the
•
appropriate time zone. This also applies to all client systems and the separate database
machine in RHN Satellite Server with Stand-Alone Database.
Confirm the correct package:
•
rhn-org-httpd-ssl-key-pair-MACHINE_NAME-VER-REL.noarch.rpm
is installed
rhn-org-trusted-ssl-cert-*.noarch.rpm
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 Requirements.

7.5. 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. 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
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...
* copying configuration information
* copying logs
* querying RPM database (versioning of RHN Satellite, etc.)
* querying schema version and database character sets
* get diskspace available
* timestamping
on the RHN
/etc/rhn/rhn.conf
Satellite Server
or raw CA SSL public (client)
satellite-debug
:
and the corresponding
. To use this tool,
55