[Linux-HA] Strange issues with my ha setup
Richard.Marshall at Arbella.com
Thu Oct 1 07:29:05 MDT 2009
We use SLES 10.1 (SP1) HA version 2.8.
Things work OK, but when something goes wrong it very difficult to
isolate the issue, HA log entries are cryptic and trying to find what
they mean is next to impossible.
Richard Marshall | Senior Technical Specialist | Arbella Insurance Group
1900 Crown Colony Drive | Quincy, MA 02269 | ': 617.328.2921| 7:
617.515.2491 | *: Richard.Marshall at Arbella.com
From: linux-ha-bounces at lists.linux-ha.org
[mailto:linux-ha-bounces at lists.linux-ha.org] On Behalf Of Timothy Carr
Sent: Thursday, October 01, 2009 9:03 AM
To: General Linux-HA mailing list
Subject: Re: [Linux-HA] Strange issues with my ha setup
Which version of Linux Heartbeat are you using ?
What has worked well for me is Linux HA v2. Ensure that you setup the
hosts correct like you have setup in your hosts file. I make use of
"hb_gui" to setup my resources Make use of the VIP resource agent for
your virtual ip addressing. I make use of 2 nic's for the public /
Hope this helps
On Thu, Oct 1, 2009 at 3:09 AM, Shadus <shadus at gmail.com> wrote:
> 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
> 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: 2009/08/06_10:03:23 ERROR: Cannot locate
> resource script mach2.domain.tld
> ResourceManager: 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.
> 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
> mach1.domain.tld 22.214.171.124/21 126.96.36.199/21 188.8.131.52/21 named
> mach2.domain.tld 184.108.40.206/21 220.127.116.11/21 18.104.22.168/21
> 22.214.171.124/24 named
> 127.0.0.1 localhost.localdomain localhost 126.96.36.199 mach1.domain.tld
> 188.8.131.52 mach2.domain.tld
> search domain.tld
> nameserver 127.0.0.1
> nameserver 184.108.40.206
> nameserver 220.127.116.11
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> See also: http://linux-ha.org/ReportingProblems
University of Cape Town
Gtalk: timothy.carr at foxtrail.co.za
Sent from Cape Town, Western Cape, South Africa
Linux-HA mailing list
Linux-HA at lists.linux-ha.org
See also: http://linux-ha.org/ReportingProblems
This email message is intended only for the addressee(s) and contains information that may be confidential.
If you are not the intended recipient please notify the sender by reply email and immediately delete this message.
Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited.
More information about the Linux-HA