Installation guide

Q:
A:
Q:
A:
RHN_PARENT: satellite.rhn.redhat.com
Error reported from RHN: <Fault -2: 'unhandled internal exception:
unsupported version: 115'>
ERROR: unhandled XMLRPC fault upon rem ote activation: <Fault -2:
'unhandled internal exception: unsupported version: 115'>
ERROR: <Fault -2: 'unhandled internal exception: unsupported version:
115'>
Invalid satellite certificate
To resolve this issue, contact Red Hat s upport services for a new certificate.
I'm ge tt ing a n "Interna l Serve r Error" complaining about ASCII when I try t o edit the
kickst art profile. What's going on?
If you have recently added some kernel parameters to your kickstart profile, you might find that
when you attempt to View a List of Kickstart Profiles that you get the following Internal
Server Error:
'ascii' codec can't encode character u'\u2013'
This error occurs because some text in the profile is not being recognised correctly.
To resolve the iss ue:
1. Ssh directly onto the Satellite server as the root user:
ssh [e-mail]
2. Find the kickstart profile that is causing the problem by looking at the dates of the files in
/var/lib/cobbler/config/profiles.d and locating the one that was edited most
recently:
ls -l /var/lib/cobbler/config/profiles.d/
3. Open the profile in your preferred text editor, and locate the following text:
\u2013hostname
Change the entry to read:
--hostname
4. Save changes to the profile and close the file.
5. Restart the RHN Satellite services to pick up the updated profile:
rhn-satellite restart
Shutting down rhn-satellite...
Stopping RHN Taskomatic...
Stopped RHN Taskomatic.
Stopping cobbler daemon: [ 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 tomcat5: [ 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 interface can take some time to resolve the services ,
but should return to normal after a minute or so.
I'm ge tt ing "Host Not Found" or "Could Not Determine FQ DN" errors. What do I do now?
Becaus e RHN configuration files rely exclus ively on fully qualified domain names (FQDNs), it is
imperative that key applications are able to resolve the name of the RHN Satellite into an IP
address. Red Ha t Update Agent, Red Ha t Ne twork Regist ra tion 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 s erver'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 s erver 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 thi s_machi ne.exampl e.com this_machi ne l ocalhost.l ocaldomain \
lo cal host
First, in a text editor, remove the offending machine information, like so:
127.0.0.1 l ocalhost.l ocaldomain.co m local host
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 :
Chapter 7. Troubleshooting
33