Installation guide

A:
Q:
A:
Q:
A:
Make sure /etc/sysconfig/rhn/systemid is owned by root.apache with the permissions
0640.
Read the log files. A list is available on the Log Files section of the Red Hat Satellite Proxy
Installation Guide.
How do I troubleshoot general problems in the Red Hat Satellite Proxy?
To begin troubleshooting general problems, examine the log file or files related to the component
exhibiting failures.
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 stops 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 various
components. T his can be done for the Apache Web server and Squid.
To obtain the status of the Apache Web server, run the command:
service httpd status
To obtain the status of Squid, run the command:
service squid status
If the administrator is not getting email from the Red Hat Satellite Proxy, confirm the correct email
addresses have been set for traceback_mail in /etc/rhn/rhn.conf.
My Red Hat Satellit e Proxy encountered the error "Host Not Found"/"Could not
Determine FQDN". What should I do?
Because Red Hat Network configuration files rely exclusively on fully qualified domain names
(FQDN), it is imperative that key applications are able to resolve the name of the Red Hat Satellite
Proxy into an IP address. Red Hat Update Agent, Red Hat Network Registration Client, and the
Apache Web server are particularly prone to this problem with the Red Hat Network applications
issuing errors of "host not found" and the Web server stating "Could not determine the server's
fully qualified domain name" upon failing to start.
This problem originates from the /etc/hosts file. Confirm this by examining the
/etc/nsswitch.conf file, which defines the methods and the order by which domain names are
resolved. Usually, the /etc/hosts file is checked first, followed by Network Information Service
(NIS) if it is being used, followed by DNS. One of these has to succeed for the Apache Web server
to start and the Red Hat Network client applications to work.
To resolve this problem, identify the contents of the /etc/hosts file. It may look like this:
127.0.0.1 this_m achine.example.com this_machine localhost.localdomain \
localhost
Red Hat Satellite 5.6 Reference Guide
84