
General Problems
57
Component/Task Log File Location
RHN Satellite Synchronization
Tool
/var/log/rhn/rhn_server_satellite.log
Monitoring infrastructure /var/log/nocpulse/ directory
Monitoring notifications /var/log/notification/ directory
RHN DB Control - Embedded
Database
/var/log/rhn/rhn_database.log
RHN Task Engine (taskomatic) /var/log/messages
yum /var/log/yum.log
XML-RPC transactions /var/log/rhn/rhn_server_xmlrpc.log
7.3. 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
yum list on Red Hat Enterprise Linux 5 (or up2date --list on earlier Red Hat Enterprise Linux
versions). 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:
df -h
In addition to log files, you can obtain valuable information by retrieving the status of your RHN
Satellite and its various components. This can be done with the command:
/usr/sbin/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 /etc/hosts file may be incorrect. Refer
to Section 7.4, “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.8.1.1, “Maintaining the RHN Task Engine”.
To obtain the status of the Satellite's Embedded Database, if it exists, run the command:
Komentarze do niniejszej Instrukcji