[Spacewalk-list] [rhn-satellite-users] Client Configuration Guide: 2.2.4. Implementing Server Failover

[Aaron Prayther]

The first error is expected, turned off satellite.  The second failure is not expected and works if set as primary.

[Wed Jan 19 10:11:30 2011] up2date An error occured talking to host1:
socket.error
(111, 'Connection refused')
Trying the next serverURL: https://host2/XMLRPC

[Wed Jan 19 10:11:30 2011] up2date A socket error occurred: (111, 'Connection refused'), attempt #1
[Wed Jan 19 10:11:30 2011] up2date Error communicating with server. The message was:
Connection refused

aaron

-----Original Message-----
From: rhn-satellite-users-bounces at redhat.com [mailto:rhn-satellite-users-bounces at redhat.com] On Behalf Of inode0
Sent: Wednesday, January 19, 2011 9:51 AM
To: spacewalk-list at redhat.com; rhn-satellite-users at redhat.com
Subject: Re: [rhn-satellite-users] Client Configuration Guide: 2.2.4. Implementing Server Failover

On Wed, Jan 19, 2011 at 8:30 AM, Aaron Prayther <aprayther at lce.com> wrote:
> I don't care about this specific functionality but do need a solution so
> that I can take one satellite down for maintenance and redirect clients
> to another (totally avoiding having a standalone instance of oracle).
> It starts getting kinda tough when you have to worry about the database
> and https.  Any ideas?

I've been using failover for several years now in a different context,
RHN proxy server connected to hosted where we used the proxy server as
primary and the RHN hosted as secondary. You should see some logging
about the failed attempts in /var/log/up2date that might give you more
information about what is failing.

John

--
rhn-satellite-users mailing list
rhn-satellite-users at redhat.com
https://www.redhat.com/mailman/listinfo/rhn-satellite-users