Red Hat NETWORK SATELLITE 5.1.1 - RELEASE NOTES, Руководство по установке

Страница: 53 / 74

Host Not Found/Could Not Determine FQDN
49
Next, restart the importation or synchronization.
If
up2date
or the push capability of the RHN Satellite Server ceases to function, it is possible that
old log files may be at fault. Stop the jabberd daemon before removing these files. To do so, issue the
following commands as root:
service jabberd stop
cd /var/lib/jabberd
rm -f _db*
service jabberd start
7.3. Host Not Found/Could Not Determine FQDN
Because RHN configuration files rely exclusively on fully qualified domain names (FQDN), it is
imperative key applications are able to resolve the name of the RHN Satellite Server into an IP
address.
Red Hat Update Agent
,
Red Hat Network Registration Client
, and the Apache Web server
are particularly prone to this problem with the RHN applications issuing errors of "host not found" and
the Web server stating "Could not determine the server's fully qualified domain name" upon failing to
start.
This problem typically originates from the
/etc/hosts
file. You may confirm this by examining
/etc/
nsswitch.conf
, which defines the methods and the order by which domain names are resolved.
Usually, the
/etc/hosts
file is checked first, followed by Network Information Service (NIS) if used,
followed by DNS. One of these has to succeed for the Apache Web server to start and the RHN client
applications to work.
To resolve this problem, identify the contents of the
/etc/hosts
file. It may look like this:
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 localhost123.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.4. 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.