28
Chapter 6. Troubleshooting
6.7. Caching Issues
If package delivery fails or an object appears to be corrupt, and it isn’t related to connection errors, you
should consider clearing the caches. The RHN Proxy Server has two caches you should be concerned
with: one for Squid and the other for authentication.
The Squid cache is located in
/var/spool/squid/
. To clear it, stop the Apache HTTP Server and
Squid, delete the contents of that directory, and restart both services. Issue these commands in this
order:
service httpd stop
service squid stop
rm -fv /var/spool/squid/*
service squid start
service httpd start
You may accomplish the same task more quickly by just clearing the directory and restarting squid,
but you will likely receive a number of RHN traceback messages.
The internal caching mechanism used for authentication by the Proxy may also need its cache cleared.
To do this, issue the following command:
rm -fv /var/cache/rhn/*
Although the RHN Authentication Daemon was deprecated with the release of RHN Proxy Server
3.2.2 and replaced with the aforementioned internal authentication caching mechanism, the daemon
may still be running on your Proxy. To turn it off, issue the following individual commands in this
order:
chkconfig --level 2345 rhn_auth_cache off
service rhn_auth_cache stop
To clear its cache, issue:
rm /var/up2date/rhn_auth_cache
If you must retain the RHN Authentication Daemon, which Red Hat recommends against and does
not support, note that its performance can suffer from verbose logging. For this reason, its logging
(to
/var/log/rhn/rhn_auth_cache.log
) is turned off by default. If you do run the daemon and
desire logging, turn it back on by adding the following line to the Proxy’s
/etc/rhn/rhn.conf
file:
auth_cache.debug = 2
6.8. Proxy Debugging by Red Hat
If you’ve exhausted these troubleshooting steps or want to defer them to Red Hat Network profes-
sionals, Red Hat recommends you take advantage of the strong support that comes with RHN Proxy
Server. The most efficient way to do this is to aggregate your Proxy’s configuration parameters, log
files, and database information and send this package directly to Red Hat.
RHN provides a command line tool explicitly for this purpose: The
RHN Proxy Diagnostic Info
Gatherer
, commonly known by its command
rhn-proxy-debug
. To use this tool, simply issue that
command as root. You will see the pieces of information collected and the single tarball created, like
so:
[root@rhel-4 root]# rhn-proxy-debug
Collecting and packaging relevant diagnostic information.
Warning: this may take some time...
Summary of Contents for NETWORK PROXY SERVER 3.6 -
Page 1: ...RHN Proxy Server 3 6 Installation Guide ...
Page 4: ......
Page 12: ...8 Chapter 2 Requirements ...
Page 16: ...12 Chapter 3 Example Topologies ...
Page 28: ...24 Chapter 5 RHN Package Manager ...
Page 34: ...30 Chapter 6 Troubleshooting ...
Page 36: ...32 Appendix A Sample RHN Proxy Server Configuration File ...
Page 38: ......