Red Hat NETWORK PROXY SERVER 4.0 Installation Manual

Red Hat NETWORK PROXY SERVER 4.0 Installation Manual Manual pdf 36 page image

32 Chapter 6. TroubleshootingComponent Log File LocationRed Hat Update Agent /var/log/up2dateTable 6-1. Log Files6.3. Questions and AnswersThis section contains the answers to the most frequently asked questions regarding in-stalling and configuring an RHN Proxy Server solution.1. After configuring the RHN Package Manager how can I determine if the local packageswere successfully added to the private RHN channel?Use the command rhn_package_manager -l -c "name_of_private_channel" tolist 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 fromthe private RHN channel.2. How can I determine whether the clients are connecting to the Squid server?The /var/log/squid/access.log file logs all connections to the Squid server.3. The Red Hat Update Agent on the client systems will not connect through the RHNProxy Server. How can I resolve this error?Make sure the latest version of the Red Hat Update Agent is installed on the clientsystems. The latest version contains features necessary to connect through an RHNProxy Server. The latest version can be obtained through the Red Hat Networkor from http://www.redhat.com/support/errata/. Also, be advised that since theRHN Proxy Server acts as a caching mechanism for RHN, the httpProxy settingin /etc/sysconfig/rhn/up2date on client systems is redundant and probablyunnecessary.The RHN Proxy Server is an extension of Apache. See Table 6-1 for its log file location.4. My RHN Proxy Server configuration does not work. Where do I begin troubleshootingit?Make sure /etc/sysconfig/rhn/systemid is owned by root.apache with the permis-sions 0640.Read the log files. A list is available at Table 6-1.