Installation guide

Q:
A:
# rhn-satellite restart
Shutting down rhn-satellite...
Stopping RHN Taskomatic...
Stopped RHN Taskom atic.
Stopping cobbler daem on: [ OK ]
Stopping rhn-search...
Stopped rhn-search.
Stopping MonitoringScout ... [ OK ]
Stopping Monitoring ... [ OK ]
Stopping httpd: [ OK ]
Stopping tomcat5: [ OK ]
Shutting down osa-dispatcher: [ OK ]
Shutting down Oracle Net Listener ... [ OK ]
Shutting down Oracle DB instance "rhnsat" ... [ OK ]
Shutting down Jabber router: [ OK ]
Done.
Starting rhn-satellite...
Starting Jabber services [ OK ]
Starting Oracle Net Listener ... [ OK ]
Starting Oracle DB instance "rhnsat" ... [ OK ]
Starting osa-dispatcher: [ OK ]
Starting tom cat5: [ OK ]
Starting httpd: [ OK ]
Starting Monitoring ... [ OK ]
Starting MonitoringScout ... [ OK ]
Starting rhn-search...
Starting cobbler daemon: [ OK ]
Starting RHN Taskomatic...
Done.
6. Return to the web interface. Note that the interface can take some time to resolve the
services. It should return to normal after some time.
I'm getting "Host Not Found" or "Could Not Determine FQDN" errors. What do I do now?
Because Red Hat Network configuration files rely exclusively on fully qualified domain names
(FQDNs), it is imperative that key applications are able to resolve the name of the Red Hat Satellite
into an IP address. Red Hat Update Agent, Red Hat Net work Registration Client, and the
Apache Web server are particularly prone to this problem with the Red Hat Network 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 Red Hat Network 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_m achine.example.com this_machine localhost.localdomain \
localhost
First, in a text editor, remove the offending machine information, like so:
Chapter 5. Troubleshooting
75