Building a Two-Node Linux Cluster with Heartbeat

Greetings:

I have configured MQ HA with heartbeat, we are running on Red Hat server. When I stop the heartbeat the failover is working fine, but when I stop the MQ or httpd, which are in resource group, node is not failing over. I mean there is no reponse from heartbeat, simply the application is stopping.
I am starting the heartbeat from /etc/rc.d/init.d/heartbeat start
How do I monitor the application health, if there is any problem with that application it should failover to the next node.
The httpd is default application with Redhat, where we can check the status with /etc/rc.d/init.d/httpd status.
When I stopped it is showing me as stopped or not running.
Do I need to do any OS configuration to keep the heartbeat always check the applications in the resources. I am new to Linux admin.

Thanks,
Chandra.

Hi,
Is it possible to have a 2 Nodes running different versions of Heartbeat(1.x/2.x) and different RHEL versions(RHEL3/RHEL4) to work well in tandem? Does failover and other heartbeat functionalities work fine in such a linux cluster?
Thanks in advance!!

Hi,
Thanks for providing such a good article.
Iam trying to setup heartbeat with the following configuration.
However,Iam having issue in VIP failover once the node1 is down.
heartbeat is not allocating the shared VIP on node2 in case node1 is down.

A:Master
eth1 = 192.168.100.2

B:Slave
eth1 = 192.168.100.4

on A eth1:2 = 192.168.100.24 (virtual interface for heartbeat)

ha.cf:
-------
logfile /var/log/ha-log
keepalive 2
deadtime 10
warntime 5
initdead 30
ucast eth1
auto_failback on
respawn hacluster /usr/lib/heartbeat/ipfail
node A
node B
ping 192.168.1.1 ( this is a gateway IP)

haresource:
============
B 192.168.223.24 mysql

authkeys:
==========
auth 2
2 sha1 Test_HB!

Node: A (3f36b1d6-90c0-4f61-9d76-f5bedee43c12): online
Node: B (7caa9321-001d-473c-b505-7081e4ec4d7f): online

Can someone plz help in resolving the issue.
Iam unable to find the reason for failure.
Thankyou.

Hi, my name is Cantek. I am from Turkey. I am trying to make a server application without application server softwares. My server will only use tcp sockets and recieve bytes and send bytes not anything more. I need a clustering and failover mechanism for my server side. I am using two ubuntu server, both has server application, during my researches i saw heartbeat so many.
What i need is ;
When my server one fails server 2 must be keep doing the job exactly at the same point where server2 failed.
Session and state informations must be kept.
If you can help me about that subject i will be very happy.
Good Days.

The ifconfig listings for node 2 I believe are incorrect. The inet address for eth0 should be 192.168.1.3 *not* 192.168.1.2.

Sharing the same address as node 1 would create a conflict.

heartbeat is excellent. If you do this for Apache, use ldirectord for load balancing and redundancy then use heartbeat to have ldirectord on two servers for fail-over redundancy.

ISC DHCP already supports multiple nodes in fail-over mode and is somewhat load balanced.

Defrag does not recover lost clusters.

SAN stands for Storage Area Network not Server Area Network.

The discussion about the MAC/ARP on a switch is incorrect and there is no need to run this set up on a hub.

When the secondary node in this type of failover happens, shouldn't the virtual IP on the new node have the same physical (MAC) address of the old one? If not, won't this confuse the hell out of the switch that it's attached to?

If you want to see a small sampling of the kinds of mission critical applications people doing on heartbeat, then you might want to look here:

http://linux-ha.org/heartbeat/users.html

Heartbeat has been in production for several years, and is in use in hundreds of mission-critical sites across the world.

I've been using Heartbeat for over a year to provide high-availability to a mission critical application.

The application employs a replicated (2-way) database, a servlet container, and several batch processes.

I've augmented Heartbeat with a program that monitors all critical resources needed by the application. It initiates a Heartbeat failover should any of these resources become unuseable.

This combination has worked flawlessly.

Be careful running any process like DHCP in this scenario! If the DHCP database from the master server is not being replicated to the HA backup, whenever the HA backup takes over it will begin assigning IP Addresses to machines regardless of what the master was already assigning (ie: A station that gets a DHCP address after restart will probably get a duplicate IP address to a system already running).

This sound more like a backup solution right? When I first saw the title, I thought it was talking about Beowulf, I guess I was wrong.

Most Windows users are probably familiar with lost clusters--something that can be rectified by running the defrag utility.

Now... Running defrag to recover lost clusters isn't a good idea. I'd rather run scandisk, or in the good old days, chkdsk /f. But then again, I don't use Microsoft products any longer ;P