Host Not Found/Could Not Determine Fqdn - Red Hat NETWORK SATELLITE SERVER 4.1.0 Installation Manual

Chapter 7. Troubleshooting 53
rhn-schema-version
To derive the character set types of your Satellite's database, run the command:
rhn-charsets
If the administrator is not getting email from the RHN Satellite Server, confirm the correct
email addresses have been set for in .
traceback_mail /etc/rhn/rhn.conf
If the traceback mail is marked from dev-null@rhn.redhat.com and you would like the
address to be valid for your organization, include the option
web.default_mail_from
and appropriate value in .
/etc/rhn/rhn.conf
If importing/synchronizing a channel fails and you can't recover it in any other way, run
this command to delete the cache:
rm -rf temporary-directory
Note that Section 6.2.2.1 Preparing Channel Content ISOs suggested that this temporary
directory be .
/var/rhn-sat-import/
Next, restart the importation or synchronization.
If or the push capability of the RHN Satellite Server ceases to function, it is
up2date
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 HTTP 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 file. You may confirm this by
/etc/hosts
examining , which defines the methods and the order by which
/etc/nsswitch.conf
domain names are resolved. Usually, the file is checked first, followed by
/etc/hosts
Network Information Service (NIS) if used, followed by DNS. One of these has to succeed
for the Apache HTTP Server to start and the RHN client applications to work.