Table of Contents
Advertisement
42
Chapter 7. Troubleshooting
In addition to log files, you can obtain valuable information by retrieving the status of your RHN
Satellite Server and its various components. This can be done with the command:
service rhn-satellite status
In addition, you can obtain the status of components such as the Apache HTTP Server and the RHN
Task Engine individually. For instance, to view the status of the Apache HTTP Server, run the com-
mand:
service httpd status
If the Apache HTTP Server isn't running, entries in your
file may be incorrect. Refer
/etc/hosts
to Section 7.3 Host Not Found/Could Not Determine FQDN for a description of this problem and
possible solutions.
To obtain the status of the RHN Task Engine, run the command:
service taskomatic status
For more information, see Section 8.7.1.1 Maintaining the RHN Task Engine.
To obtain the status of the Satellite's Embedded Database, if it exists, run the command:
service rhn-database status
To determine the version of your database schema, run the command:
rhn-schema-version
To derive the character set types of your Satellite's database, run the command:
rhn-charsets
If the administrator isn't getting email from the RHN Satellite Server, confirm the correct email ad-
dresses have been set for
in
.
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 and appropriate value in
web.default_mail_from
.
/etc/rhn/rhn.conf
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 Preparing for Import suggested this temporary directory be
.
/var/rhn-sat-import/
Then restart the importation or synchronization.
7.3. Host Not Found/Could Not Determine FQDN
Because RHN configuration files rely exclusively on fully qualified domain names (FQDN), it is
imperative key applications are able to resolve the name of the RHN Satellite Server into an IP address.
Red Hat Update Agent, Red Hat Network Registration Client, and the Apache HTTP Server are
particularly prone to this problem with the RHN applications issuing errors of "host not found" and
the Web server stating "Could not determine the server's fully qualified domain name" upon failing to
start.
Advertisement
Table of Contents
