Red Hat NETWORK PROXY 5.3.0 -, Руководство по установке

Страница: 30 / 48

Chapter 6. Troubleshooting
26
rhn-org-httpd-ssl-key-pair- MACHINE_NAME-VER-REL .noarch.rpm
is installed on the RHN Proxy Server and the corresponding
rhn-org-trusted-ssl-cert-
*.noarch.rpm
or raw CA SSL public (client) certificate is installed on all client systems.
• Verify the client systems are configured to use the appropriate certificate.
• If using one or more RHN Proxy Servers, ensure each Proxy's SSL certificate is prepared correctly.
If using the RHN Proxy Server in conjunction with an RHN Satellite Server the Proxy should have
both its own server SSL key-pair and CA SSL public (client) certificate installed, since it will serve
in both capacities. Refer to the SSL Certificates chapter of the
RHN Client Configuration Guide
for
specific instructions.
• If the RHN Proxy Server is connecting through an HTTP Proxy, make sure the URL listed is valid.
For instance, the HTTP Proxy URL field should not contain references to protocols, such as http:// or
https://. Only the hostname and port should be included in the form hostname:port, such as
your-
gateway.example.com:8080
.
• Make sure client systems are not using firewalls of their own blocking required ports, as identified in
Section 2.4, “Additional Requirements”
.
6.7. Caching Issues
If package delivery fails or an object appears to be corrupt, and it is not 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 Web 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: