Red Hat NETWORK SATELLITE 5.0.0 Installation Manual page 60

Chapter 7. Troubleshooting
component exhibiting failures. A useful exercise is to issue the
files and then run
up2date --list
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 Web server and the
RHN Task Engine individually. For instance, to view the status of the Apache Web server, run
the command:
service httpd status
If the Apache Web server isn't running, entries in your
to Section 3, "Host Not Found/Could Not Determine FQDN"
possible solutions.
To obtain the status of the RHN Task Engine, run the command:
service taskomatic status
For more information, see
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
54
. You should then examine all new log entries for potential
Section 7.1.1, "Maintaining the RHN Task
command for all log
tail -f
file may be incorrect. Refer
/etc/hosts
for a description of this problem and
Engine".