Table of Contents
Advertisement
52
Component/Task
Red Hat Update Agent
XML-RPC transactions
Table 7-1. Log Files
7.2. General Problems
To begin troubleshooting general problems, examine the log file or files related to the
component exhibiting failures. A useful exercise is to issue the
log files and then run
potential clues.
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 stopped 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
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 command:
service httpd status
If the Apache HTTP Server isn't running, entries in your
rect. Refer 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:
Log File Location
/var/log/up2date
/var/log/rhn/rhn_server_xmlrpc.log
up2date --list
. You should then examine all new log entries for
/etc/hosts
Chapter 7. Troubleshooting
command for all
tail -f
file may be incor-
Advertisement
Table of Contents
