Red Hat NETWORK SATELLITE 5.3.0 Installation Manual

Also see for NETWORK SATELLITE 5.3.0 - CHANNEL MANAGEMENT: Installation guide Management guide Configuration guide Installation guide Release note

Contents

Red Hat NETWORK SATELLITE 5.3.0 Installation Manual Manual pdf 62 page image

Chapter 7. Troubleshooting58If the administrator is not getting email from the RHN Satellite, confirm the correct email addresseshave been set for traceback_mail in /etc/rhn/rhn.conf.If the traceback mail is marked from dev-null@rhn.redhat.com and you would like the address to bevalid for your organization, include the web.default_mail_from option 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 commandto delete the cache:rm -rf temporary-directoryNote that Section 6.2.2.1, “Preparing Channel Content ISOs” suggested that this temporary directorybe /var/rhn-sat-import/.Next, restart the importation or synchronization.If yum (or up2date) or the push capability of the RHN Satellite ceases to function, it is possible thatold log files may be at fault. Stop the jabberd daemon before removing these files. To do so, issue thefollowing commands as root:service jabberd stopcd /var/lib/jabberdrm -f _db*service jabberd start7.4. Host Not Found/Could Not Determine FQDNBecause RHN configuration files rely exclusively on fully qualified domain names (FQDN), it isimperative key applications are able to resolve the name of the RHN Satellite into an IP address.Red Hat Update Agent, Red Hat Network Registration Client, and the Apache Web server areparticularly prone to this problem with the RHN applications issuing errors of "host not found" and theWeb 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 clientapplications 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 \ localhostFirst, in a text editor, remove the offending machine information, like so:127.0.0.1 localhost.localdomain.com localhost