Installation guide

32 Chapter 6. Troubleshooting

Table 6-1. Log Files

6.3. Questions and Answers

This section contains the answers to the most frequently asked questions regarding in-

stalling and conﬁguring an RHN Proxy Server solution.

1. After conﬁguring the RHN Package Manager how can I determine if the local packages

were successfully added to the private RHN channel?

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 inter-

face.

After subscribing a registered system to the private channel, you can also execute the com-

mand up2date -l --showall on the registered system and look for the packages from

the private RHN channel.

2. How can I determine whether the clients are connecting to the Squid server?

The /var/log/squid/access.log ﬁle logs all connections to the Squid server.

3. The Red Hat Update Agent on the client systems does not connect through the RHN

Proxy Server. How can I resolve this error?

Make sure that the latest version of the Red Hat Update Agent is installed on the client

systems. The latest version contains features necessary to connect through an RHN Proxy

Server. The latest version can be obtained through the Red Hat Network by issuing the com-

mand up2date up2date as root or from http://www.redhat.com/support/errata/. Also,

be advised that since the RHN Proxy Server acts as a caching mechanism for RHN, the

httpProxy setting in /etc/sysconfig/rhn/up2date on client systems is redundant

and probably unnecessary.

The RHN Proxy Server is an extension of Apache. See Table 6-1 for its log ﬁle location.

4. My RHN Proxy Server conﬁguration does not work. Where do I begin troubleshooting

it?

Make sure /etc/sysconfig/rhn/systemid is owned by root.apache with the permis-

sions 0640.

Read the log ﬁles. A list is available at Table 6-1.