Red Hat NETWORK SATELLITE 5.1.1 - RELEASE NOTES, Installation Manual

Page: 51 / 74

Chapter 7.
47
Troubleshooting
This chapter provides tips for determining the cause of and resolving the most common errors
associated with RHN Satellite Server. If you need additional help, contact Red Hat Network support at
https://rhn.redhat.com/help/contact.pxt
. Log in using your Satellite-entitled account to see your full list
of options.
In addition, you may package configuration information and logs from the Satellite and send them to
Red Hat for further diagnosis. Refer to
Section 7.6, “Satellite Debugging by Red Hat”
for instructions.
7.1. Log Files
Virtually every troubleshooting step should start with a look at the associated log file or files. These
provide invaluable information about the activity that has taken place on the device or within the
application that can be used to monitor performance and ensure proper configuration. See
Table 7.1,
“Log Files”
for the paths to all relevant log files:
Component/Task Log File Location
Apache Web server
/var/log/httpd/
directory
RHN Satellite Server
/var/log/rhn/
directory
RHN Satellite Server Installation
Program
/var/log/rhn_satellite_install.log
Database installation -
Embedded
Database
/var/log/rhn/rhn-database-installation.log
Database population
/var/log/rhn/populate_db.log
RHN Satellite Synchronization
Tool
/var/log/rhn/rhn_server_satellite.log
Monitoring infrastructure
/home/nocpulse/var/
directory
Monitoring notifications
/opt/notification/var/
directory
RHN DB Control
-
Embedded
Database
/var/log/rhn/rhn_database.log
RHN Task Engine
(taskomatic)
/var/log/messages
Red Hat Update Agent
/var/log/up2date
XML-RPC transactions
/var/log/rhn/rhn_server_xmlrpc.log
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
tail -f
command for all log files and then run
up2date --list
. You should then examine all new log entries for 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: