Caching Issues; Satellite Debugging By Red Hat - Red Hat NETWORK SATELLITE SERVER 3.7 Installation Manual

46
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
•
is installed
rhn-org-trusted-ssl-cert-*.noarch.rpm
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 (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. Caching Issues

If importing or synchronizing fails, and it isn't related to connection errors, you should consider
clearing the cache. By default, the cache is located in
the command:
rm -fv /var/cache/rhn/*
In addition, you may set the cache refresh level for all importing and synchronizing using the
--cache-refresh-level
the cache entirely upon initialization and closure. Refer to Section 6.1.3 Import/Sync Cache Refresh
for information on the available levels.

7.6. Satellite Debugging by Red Hat

If you've exhausted these troubleshooting steps or want to defer them to Red Hat Network profession-
als, 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 Gath-
erer, commonly known by its command
mand 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 charactersets
* get diskspace available
* timestamping
* 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.
rhn-org-httpd-ssl-key-pair-MACHINE_NAME-VER-REL.noarch.rpm
on the RHN
option of
satellite-sync
satellite-debug
Satellite Server
or raw CA SSL (client) certificate is installed
/var/cache/rhn/
. Setting this to its highest level removes
. To use this tool, simply issue that com-
Chapter 7. Troubleshooting
and the corresponding
. To clear it manually, issue