To begin troubleshooting general problems, examine the log file or files related to the component exhibiting failures. A useful exercise is to tail 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:
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 /etc/hosts file may be incorrect. 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:
rhn-schema-version |
To derive the character set types of your Satellite's database, run the command:
rhn-charsets |
If the administrator isn't getting email from the RHN Satellite Server, confirm the correct email addresses have been set for traceback_mail in /etc/rhn/rhn.conf.
If the traceback mail is marked from [email protected] and you would like the address to be valid for your organization, include the web.default_mail_from option and appropriate value in /etc/rhn/rhn.conf.
If importing/synchronizing a channel fails and you can't recover it in any other way, run this command to delete the cache:
rm -rf temporary-directory |
Note that Section 6.2.2 Preparing for Import suggested this temporary directory be /var/rhn-sat-import/.
Then restart the importation or synchronization.