You can do the following with an external DB and a cname. This is not an
active/active solution, but active/standby. This method has it's own
pros and cons.
1. Install spacewalk/satellite (same version) on one server at location x
and another server at location y (do not update schema on the second
install).
Ensure that during the install on both servers:
update /etc/hosts 1st line to be the cname on both
servers
set hostname to the cname.
Create the following soft link. Some wrapper scripts are hard
coded to look in /usr/shar/rhn
ln -s
/var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT
/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
2. chkconfig all spacewalk components off.
for spacewlk in `/usr/sbin/rhn-satellite list |grep "4:" |awk
'{print $1}'`; do /usr/sbin/rhn-satellite disable $spacewlk; done
NOTE: After upgrades, make sure the above is done as well.
3. Ensure that most of the spacewalk important filesystems are available
to be "switched out/ or sync'd" with location y.
WARNING: If sync'ing make sure that you have a sync back to
location x.
/etc/tomcat6
/etc/cobbler
/etc/httpd
/etc/rhn
/usr/share/rhn
/usr/share/spacewalk
/var/cache/rhn
/var/cache/tomcat6
/var/lib/cobbler
/var/lib/rhn
/var/log/cobbler
/var/log/httpd
/var/log/rhn
/var/www
/var/satellite
config/misc filesystem (that also needs to be "switched out/ or
sync'd" with location y)
mkdir -p /xxxxxx/
ln -s /xxxxxx/tnsnames.ora
/usr/lib/oracle/11.2/client64/lib/network/admin/tnsnames.ora
ln -s /xxxxxx/tnsnames.or /etc/tnsnames.ora
osa-dispatcher will not start on failover unless this is done
mv /etc/pki/spacewalk/jabberd/server.pem
/xxxxxx/server_pki.pem
ln -s /xxxxxx/server_pki.pem
/etc/pki/spacewalk/jabberd/server.pem
bugzilla report --> need to do the following (files are
required to have this ownership/permissions or else)
chown -h jabber:jabber
/etc/pki/spacewalk/jabberd/server.pem
chown jabber:jabber /xxxxxx/server_pki.pem
mv /etc/jabberd/server.pem
/xxxxxx/server_jabber.pem
ln -s /xxxxxx/server_jabber.pem
/etc/jabberd/server.pem
chown -h root:jabber /etc/jabberd/server.pem
chown root:jabber /xxxxxx/server_jabber.pem
mv /etc/sysconfig/tomcat6 /xxxxxx/configs/
mv /etc/sysconfig/osa-dispatcher /xxxxxx/configs/
ln -s /xxxxxx/configs/tomcat6 /etc/sysconfig/tomcat6
ln -s /xxxxxx/configs/osa-dispatcher
/etc/sysconfig/osa-dispatcher
4. Write your own startup scripts in /etc/init.d to check if the
server has the cname, if so "update/vatlidate" /etc/hosts, hostname, and
to startup the spacewalk. If does not have cname, do nothing.
5. On failover, stop the spacewalk services, remove cname from
/etc/hosts, set hostname back to the fqdn, and swap out disk or do a final
sync to location y.
6. Update cname to point to location y and ensure nothing is
running on location y.
7. run your start script.
- Thanks and good luck.
From: Stuart Green <[email protected]>
To: "[email protected]" <[email protected]>
Date: 03/08/2016 08:17 AM
Subject: Re: [Spacewalk-list] Spacewalk Failover?
Sent by: [email protected]
This email originated from outside of the company. Please use discretion
if opening attachments or clicking on links.
I was wrong. It does not work. The systemid is regenerated each
registration, so whenever you register one client with one server, you
lose registration to the other as the systemid its expecting no longer
matches.
On 8 March 2016 at 10:54, Stuart Green <[email protected]>
wrote:
I have this working now.
The machine's are registered on both sides and pulling updates. The
default config was http which has been shutdown so an erroneous result was
being received. I also had some configuration management files causing a
problem, so I've created a new configuration channel on each server for
these machines which just contains the dual up2date config file.
Looks good!
Cheers.
On 7 March 2016 at 16:10, Stuart Green <[email protected]>
wrote:
So I've spent a bit of time getting my 2 spacewalk servers 'connected'. I
have ISS mode configured so the channels are syncing between the two
servers, the next thing I moved to was 'failover'
There's not much information on the web or on this list pertaining to
quite whether it works but documentation here suggests it can with the
correct version of up2date.
https://access.redhat.com/documentation/en-US/Red_Hat_Network/5.0.0/html/Client_Configuration_Guide/s2-client-config-failover.html
The problem is the 2 url setting never sticks, the client machine needs
to be registered with both spacewalk servers to receive the updates, and
in the process of registration the altered /etc/sysconfig/rhn/up2date file
is reverted. If I put the urls back again, then shutdown the primary
spacewalk server and try to update from the secondary it goes back to
saying I'm not registered.
Does this method actually work any more or has it been superseeded?
Cheers,
Stu
This email originated from outside of the company. Please use discretion
if opening attachments or clicking on links.
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
**
This email and any attachments may contain information that is confidential
and/or privileged for the sole use of the intended recipient. Any use, review,
disclosure, copying, distribution or reliance by others, and any forwarding of
this email or its contents, without the express permission of the sender is
strictly prohibited by law. If you are not the intended recipient, please
contact the sender immediately, delete the e-mail and destroy all copies.
**
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
