Red Hat NETWORK PROXY 5.3.0 -, Installation Manual

Page: 27 / 48

Chapter 6.
23
Troubleshooting
This chapter provides tips for determining the cause of and resolving the most common errors
associated with RHN Proxy 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.
6.1. Managing the Proxy Service
Since the RHN Proxy Server consists of a multitude of individual components, Red Hat provides a
script called
rhn-proxy
, that allows you to stop, start, or retrieve status on the Proxy.
/usr/sbin/rhn-proxy start
/usr/sbin/rhn-proxy stop
/usr/sbin/rhn-proxy restart
/usr/sbin/rhn-proxy status
Use the
rhn-proxy
command to shut down and start the entire RHN Proxy Server and retrieve status
messages from all of its services at once.
6.2. Log Files
Virtually every troubleshooting step should start with a look at the associated log file or files. These
files provide invaluable information about the activity that has taken place on the device or within the
application and can be used to monitor performance and ensure proper configuration. See
Table 6.1,
“Log Files”
for the paths to all relevant log files:
Component Log File Location
Apache Web server
/var/log/httpd/
directory
Squid
/var/log/squid/
directory
RHN Proxy Broker Server
/var/log/rhn/rhn_proxy_broker.log
RHN SSL Redirect Server
/var/log/rhn/rhn_proxy_redirect.log
Red Hat Update Agent
/var/log/yum.log
Table 6.1. Log Files
6.3. Questions and Answers
This section contains the answers to the most frequently asked questions regarding installing and
configuring an RHN Proxy Server solution.
Q:
After configuring the RHN Package Manager how can I determine if the local packages were
successfully added to the private RHN channel?
A:
Use the command
rhn_package_manager -l -c "name_of_private_channel"
to list
the private channel packages known to the RHN Servers. Or visit the RHN Web interface.