Installation guide
Q:
A:
127.0.0.1 l ocalhost.l ocaldomain.co m local host
123.4 5.67.8 this_machi ne.example.co m this_machi ne
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.
I'm ge tt ing a "T his se rver is not an e nt itled Sa te llit e" when I t ry t o synchronize the RHN
Sat ellit e server. How do fix it?
If satellite-sync reports that the server is not activated as an RHN Satellite, it isn't subscribed
to the res pective RHN Satellite channel. If this is a newly installed system then the satellite
certificate is possibly not activated on the system. If it was activited earlier, then it has become
deactivated.
Check the system's child channels to discover if it is subscribed to any Red Hat Network RHN
Satellite channel:
Login to Red Hat Network and search the s ystem's child channel, using one of these methods :
On a Red Hat Enterprise Linux 5 or 6 s ystem, view the channels to which the system is
subscribed with this command:
yum repolist
Activate the same Satellite certificate again on your Satellite, using this command as the root user:
rhn-satellite-activate -vvv --rhn-cert=/path/to/certificate
Note
If you've exhausted these troubleshooting steps or want to defer them to Red Hat Network
profes sionals, Red Hat recommends you take advantage of the strong support that comes with
RHN Satellite. The most efficient way to do this is to aggregate your Satellite's configuration
parameters, log files, and databas e information and send this package directly to Red Hat.
RHN provides a command line tool explicitly for this purpose: T he Sat ellite Diagnost ic Info
Ga therer, commonly known by its command satellite-debug. To us e this tool, iss ue the
command as root. You will see the pieces of information collected and the single tarball created,
like so:
[root@miab root]# satellite-debug
Collecting and packaging relevant diagnostic inform ation.
Warning: this may take som e time...
* copying configuration inform ation
* copying logs
* querying RPM database (versioning of RHN Satellite, etc.)
* querying schem a version and database character sets
* get diskspace available
* timestam ping
* creating tarball (may take some time): /tm p/satellite-debug.tar.bz2
* rem oving temporary debug tree
Debug dump created, stored in /tm p/satellite-debug.tar.bz2
Deliver the generated tarball to your RHN contact or support channel.
Once finished, email the new file from the /tmp/ directory to your Red Hat representative for
immediate diagnosis.
Red Hat Network Satellite 5.4 Installation Guide
34