I posted this to the list a month or so ago, but had no responses and it kind of dropped off the radar because of more important issues with a san/vmware cluster, but now I need to revisit it and I've come up with little to be able to help me figure out where the problem is originating precisely. Any advice or help would be greatly appreciated.
I've setup ha a couple times in the past and had no serious issues but they were simple setups... this is fairly simple also at least i thought so until it exploded :) This is just simple heartbeat. If i start heartbeat on mach2.domain.tld it brings up the ip addresses its preferred for... right until i start mach1's heartbeat at which point it takes them all down and mach1's ip addresses never come up. I'm seeing this on mach1. ResourceManager[7853]: 2009/08/06_10:03:23 ERROR: Cannot locate resource script mach2.domain.tld ResourceManager[7853]: 2009/08/06_10:03:24 info: Retrying failed stop operation [mach2.domain.tld] Furthermore the ip addresses on mach1 never come up due to the above error at least in part. Ideas? ha.cf -------- logfile /var/log/ha-log logfacility local0 udpport 694 keepalive 1 warntime 3 deadtime 6 initdead 30 bcast eth0 auto_failback on node mach1.domain.tld node mach2.domain.tld haresources ------- mach1.domain.tld 12.34.56.78/21 12.34.56.77/21 12.34.56.75/21 named mach2.domain.tld 12.34.56.79/21 12.34.56.76/21 12.34.56.74/21 55.23.41.73/24 named hosts ------- 127.0.0.1 localhost.localdomain localhost 12.23.56.70 mach1.domain.tld 12.23.56.71 mach2.domain.tld resolv.conf ------ search domain.tld nameserver 127.0.0.1 nameserver 12.34.56.78 nameserver 12.34.56.79 -- Shadus _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
