Table of Contents
Advertisement
Chapter 6. Troubleshooting
33
6.4. General Problems
To begin troubleshooting general problems, examine the log file or files related to the com-
ponent exhibiting failures. A useful exercise is to
all log files and then run
tail
up2date
. You should then examine all new log entries for potential clues.
--list
A common issue is full disk space. An almost sure sign of this is the appearance of halted
writing in the log files. If logging stops during a write, such as mid-word, you likely have
filled disks. To confirm this, run this command and check the percentages in the Use%
column:
df -h
In addition to log files, you can obtain valuable information by retrieving the status of your
various components. This can be done for the Apache HTTP Server and Squid.
To obtain the status of the Apache HTTP Server, run the command:
service httpd status
To obtain the status of Squid, run the command:
service squid status
If the administrator is not getting email from the RHN Proxy Server, confirm the correct
email addresses have been set for
in
.
traceback_mail
/etc/rhn/rhn.conf
6.5. Host Not Found/Could Not Determine FQDN
Because RHN configuration files rely exclusively on fully qualified domain names
(FQDN), it is imperative that key applications are able to resolve the name of the RHN
Proxy 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.
This problem typically originates from the
file. You may confirm this by
/etc/hosts
examining
, which defines the methods and the order by which
/etc/nsswitch.conf
domain names are resolved. Usually, the
file is checked first, followed by
/etc/hosts
Network Information Service (NIS) if used, followed by DNS. One of these has to succeed
for the Apache HTTP Server to start and the RHN client applications to work.
To resolve this problem, identify the contents of the
file. It may look like
/etc/hosts
this:
127.0.0.1
this_machine.example.com this_machine localhost.localdomain \
localhost
Advertisement
Table of Contents
