Red Hat Bugzilla – Bug 200344
up2date doesn't perform correctly for redundant satellite server configuration
Last modified: 2012-06-20 12:02:45 EDT
Description of problem:
I have attached a PDF document that I received to help me get ready for the
engagement that I am currently working on. I am on site with a customer that
has purchased two Satellite Servers with Embedded DBs. One is on site and the
other is located at their DR facility. They are both attached to their
respective mirrored (NetApp Filers) for the /var/satellite, /rhnsat,
/var/www/html/pub file systems. We have successfully failed over with some
limited manual interaction. Here is where the problem comes in....
The attached document states the up2date is capable of looking at multiple
RHN/Satellite Hosts, delimited by ";" in the /etc/sysconfig/rhn/up2date file.
If you are interested, this is stated on page 6, the second paragraph of
"Configuring the Clients".
I am unable to make this work. I am currently in the "Failed Over" mode and if
I log onto a client and remove the primary Sat Servs' URL from the serverURL
line I can up2date the system to the secondary satellite. But with both URLs on
the line I get a connection refused message from the primary and then nothing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Place two satellite server URLs separated by a ";" on the serverURL line in
/etc/sysconfig/rhn/up2date file. Example above.
2. With the first Satellite disabled attempt to perform an up2date on a
registered client. up2date -l will due to perform the test.
3. Placing an ";" at the end of the same serverURL line will correct the error.
Failure to connect; Connection Refused
Up2date performs its' requested function on whichever satellite is active.
Created attachment 133124 [details]
User firstname.lastname@example.org's account has been closed
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.