Red Hat NETWORK - USER 3.0 Guía de instalación Pagina 63

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 86
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 62
Connection Errors
59
127.0.0.1 this_machine.example.com this_machine localhost.localdomain \ localhost
First, in a text editor, remove the offending machine information, like so:
127.0.0.1 localhost.localdomain.com localhost
Then, save the file and attempt to re-run the RHN client applications or the Apache Web server. If they
still fail, explicitly identify the IP address of the Satellite in the file, such as:
127.0.0.1 localhost.localdomain.com localhost
123.45.67.8 this_machine.example.com this_machine
Replace the value here with the actual IP address of the Satellite. This should resolve the problem.
Keep in mind, if the specific IP address is stipulated, the file will need to be updated when the machine
obtains a new address.
7.5. Connection Errors
A common connection problem, indicated by SSL_CONNECT errors, is the result of a Satellite
being installed on a machine whose time had been improperly set. During the Satellite installation
process, SSL certificates are created with inaccurate times. If the Satellite's time is then corrected, the
certificate start date and time may be set in the future, making it invalid.
To troubleshoot this, check the date and time on the clients and the Satellite with the following
command:
date
The results should be nearly identical for all machines and within the "notBefore" and "notAfter" validity
windows of the certificates. Check the client certificate dates and times with the following command:
openssl x509 -dates -noout -in /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
Check the Satellite server certificate dates and times with the following command:
openssl x509 -dates -noout -in /etc/httpd/conf/ssl.crt/server.crt
By default, the server certificate has a one-year life while client certificates are good for 10 years. If
you find the certificates are incorrect, you can either wait for the valid start time, if possible, or create
new certificates, preferably with all system times set to GMT.
The following measures can be used to troubleshoot general connection errors:
Attempt to connect to the RHN Satellite's database at the command line using the correct
connection string as found in /etc/rhn/rhn.conf:
sqlplus username/password@sid
Vista de pagina 62
1 2 ... 58 59 60 61 62 63 64 65 66 67 68 ... 85 86

Comentarios a estos manuales

Sin comentarios