China wrote:
Sorry, I forgot it!
I've two connection for the PCs:
one with crossover cable, where heartbeat send packets directly to other PC
one through network, where the services listen and where pingd test
connectivity
When I force the failure I disconnect the network cable that give services
from PC_A.
Use both connections for heartbeat. Maybe use ucast on the external
interface instead of bcast.
Your supplied config file only reads one interface:
--------------
*ha.cf:
use_logd yes
compression zlib
coredumps no
keepalive 1
warntime 2
deadtime 5
deadping 5
udpport 694
bcast eth2
node test-ppc test3
ping 192.168.122.113
#respawn hacluster /rnd/apps/components/heartbeat/lib/heartbeat/ipfail
#respawn root /rnd/apps/components/heartbeat/lib/heartbeat/pingd -m 100 -d
5s
#auto_failback off
crm yes
-------------
But if it really is the way you tell, this should not cause the problem
you told about.
Just a thought: If - by any chance - you pull the plug out of the
connection that sends/receives the heartbeats, you will have a
splitbrain situation which would nicely explain the things you mentioned.
So please use both links for heartbeat cluster communication and make
sure you pull the right plug :)
Regards
Dominik
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
