The below 2 attempts to connect to a secondary satellite server (and appears to me that the secondary is never attempted) shows the first attempt when the primary satellite server (that has rhn-satellite stop: not running) and the secondary hostname1 that is up and running and works if set as primary.
The second, 2 attempt is renaming the primary (and still disabled satellite server) wronghostname so that it won't resolve. Both fail never attempting to connect to secondary/failover satellite hostname1. serverURL[comment]=Remote server URL serverURL=https://hostname/XMLRPC;https://hostname1/XMLRPC; proxyPassword[comment]=The password to use for an authenticated proxy proxyPassword= proxyUser[comment]=The username for an authenticated proxy proxyUser= disallowConfChanges[comment]=Config options that can not be overwritten by a config update action disallowConfChanges=noReboot;sslCACert;useNoSSLForPackages;noSSLServerURL;serverURL;disallowConfChanges; sslCACert[comment]=The CA cert used to verify the ssl server sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT [root@host ~]# yum --nogpg update Loaded plugins: rhnplugin, security There was an error communicating with RHN. RHN channel support will be disabled. Error communicating with server. The message was: Connection refused Setting up Update Process No Packages marked for Update [root@host ~]# vim /etc/sysconfig/rhn/up2date serverURL[comment]=Remote server URL serverURL=https://wronghostname/XMLRPC;https://hostname1/XMLRPC; proxyPassword[comment]=The password to use for an authenticated proxy proxyPassword= proxyUser[comment]=The username for an authenticated proxy proxyUser= disallowConfChanges[comment]=Config options that can not be overwritten by a config update action disallowConfChanges=noReboot;sslCACert;useNoSSLForPackages;noSSLServerURL;serverURL;disallowConfChanges; sslCACert[comment]=The CA cert used to verify the ssl server sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT [root@host ~]# yum --nogpg update Loaded plugins: rhnplugin, security There was an error communicating with RHN. RHN channel support will be disabled. Error communicating with server. The message was: Name or service not known Setting up Update Process No Packages marked for Update [root@nces-util-01 ~]# Aaron Prayther Aaron Prayther -----Original Message----- From: Miroslav Suchý [mailto:[email protected]] Sent: Tuesday, January 18, 2011 8:36 AM To: [email protected] Cc: Aaron Prayther; [email protected] Subject: Re: [Spacewalk-list] [rhn-satellite-users] Client Configuration Guide: 2.2.4. Implementing Server Failover On 01/18/2011 01:32 PM, Aaron Prayther wrote: > I'm dual posting spacewalk/satellite. > > It's a satellite issue but a relatively new feature (I think, have not > tried using it till now). Having come up empty handed on google, other > than references back to the documentation... > > It never seems to connect (or even try) to the second configured > satellite server. I have messed with registering one or the other and > changing from https to http. No matter what I do it never appears to > attempt to connect to the secondary server. > > Does anyone have any pointers on this? You may be right. Can you elaborate on which command does not use that failover? We have dozen client commands and I want to be sure we speak about the same one. -- Miroslav Suchy Red Hat Satellite Engineering _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
