mangoo at wpkg
Aug 27, 2010, 5:59 PM
Post #1 of 2
(285 views)
Permalink
|
|
3+ heartbeat nodes? failure when only 1 node is running
|
|
I'm trying to set up 3 or more heartbeat nodes, but I'm not satisfied with ow it works: if I leave only one node up, all IPs go down.
I created the setup as below:
## ha.cf
use_logd on
keepalive 500ms
deadtime 2
warntime 1
initdead 8
ping 10.1.1.1
bcast eth0
auto_failback on
crm yes
autojoin any
node server1
node server2
node server3
#########
## haresources
server1 10.1.1.10/255.255.255.255
server2 10.1.1.11/255.255.255.255
server3 10.1.1.12/255.255.255.255
#########
Then, I generated /var/lib/heartbeat/crm/cib.xml with this command:
python /usr/lib/heartbeat/haresources2cib.py
When I start heartbeat on all three nodes, they all receive their respective IP after about 30-60 seconds (which is quite long, BTW).
When I stop heartbeat on server3, one of the remaining machines will bring IP belonging to server3 up.
Now, when I stop heartbeat on server2 (thus, leaving heartbeat running on server1 only), server1 brings all "heartbeat" IPs down.
What's wrong in my configuration?
I use Ubuntu 10.04 with these packages:
ii heartbeat 1:3.0.3-1ubuntu1 Subsystem for High-Availability Linux
ii libheartbeat2 1:3.0.3-1ubuntu1 Subsystem for High-Availability Linux (libra
ii pacemaker 1.0.8+hg15494-2ubuntu2 HA cluster resource manager
--
Tomasz Chmielewski
http://wpkg.org
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
|
