strange behavior with clumanager?
"Sean Oh" <oh-/[email protected]>
| Newsgroups | gmane.linux.redhat.taroon |
|---|---|
| Message-ID | <[email protected]> |
The clumanager-1.1.82-1 RPM missed several utilities, such as clusvcadm, and etc.
The new version of clumanager, compared to AS 2.1, where is tha favorite cluadm CLI util?
Also, in the new version, how do I make the preferred member?
I have been playing around with 1.1.82 and noticed very strange behavior.
------
members:
rhel1
rhel2
Failed domain:
Services:
nfs01
192.168.0.200 <service ip address>
/dev/sdc5
/nfs01 <nfsexport>
* <client>
------
In this simple configuration, I like to have rhel1 as the prefered member and if the rhel1 is down, rhel2 takes over the service. Also, after rhel1 re-joins the cluster, rhel1 takes over the service, since rhel1 is prefered.
But, what is happending is that when rhel1 is down( I did /etc/init.d/clumanager stop in rhel1), rhel2 is auto-rebooted and service is not available at all.
I tried with a few things with failed domain, but it did not help..
Also, how do I configure additional heartbeat channel in the new clumanager?
BTW, the cluster adminiration doc need to updated. it is out-dated and does not help much.
Appreciated any help.
--
Taroon-beta-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/taroon-beta-list