Questions[heartbeat1](server)

I've installed Heartbeat in two CentOS 6.2 machines which are running http service. I want these machines to be in Active/Passive state. I want only one machine to be active. Here's my ha.cf file:

logfacility     local0
ucast   eth1    192.168.0.66
#bcast eth1
keepalive 2
warntime 6
deadtime 10
auto_failback on
use_logd yes

node    web5
node    web5b

And here's the haresources file:

web5    IPaddr::192.168.0.60/24/eth1/192.168.0.255

The problem is when I start heartbeat on both servers, the IP 192.168.0.60 stays active in both servers. I want it to be active only on Web5 and if web5 goes down it'll be active in Web5b. My heartbeat version is 3.0.4.

Any help?

I installed Heartbeat on my Centos Linux and it seems to partially work..but I'm trying to monitor a service with no success. only when I reboot the main server the backup server takes over. in the logs I get :

heartbeat[30476]: 2012/03/20_18:51:57 WARN: string2msg_ll: node [node1] failed authentication
heartbeat[30476]: 2012/03/20_18:51:58 WARN: string2msg_ll: node [node02] failed authentication

the authkeys is identical (copied from one to another). this is my ha.cf:

logfile /var/log/ha-log
logfacility local0
keepalive 2
deadtime 30
initdead 120
bcast eth0
udpport 694
auto_failback on
node server01.com 
node server02.com

haresources :

server01.com 38.108.117.3 aim chat

any idea how to fix the problem so if a service stops the other server take over Thanks! E.

I'm trying to start heartbeat on Ubuntu 10.04 with service heartbeat start, but getting the following errors:

heartbeat[24829]: 2011/11/22_19:31:07 ERROR: Bad nodename in /etc/ha.d//haresources [node1]
heartbeat[24829]: 2011/11/22_19:31:07 ERROR: Configuration error, heartbeat not started.

On on server uname -n produces loadb1, on the second server uname -n produces loadb2. The two servers can ping each other okay with those names.

This is /etc/ha.d/ha.cnf on both servers:

debugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility     local0
keepalive 2
deadtime 10
udpport 694
bcast eth1
ucast eth0 my.external.ip
ucast eth0 my.external.ip
ucast eth1 10.0.0.5
ucast eth1 10.0.0.6
#udp     eth0
node    loadb1
node    loadb2
auto_failback off

And this is /etc/ha.d/haresources on both servers:

node1 IPaddr::46.20.121.113 httpd smb dhcpd

Authkeys is also set up.

What am I doing wrong?

The part where I'm least clear is the ucast/bcast lines.

I'm setting up 2 mailservers (Postfix) with heartbeat failover & drbd shared maildirs. For some reason, when starting the heartbeat, the default gateway is lost. Any idea how / why this happens and what the solution is?

/etc/network/interfaces:

# The loopback network interface
auto lo
iface lo inet loopback

# eth0: ip of this node
auto eth0
allow-hotplug eth0
iface eth0 inet static
        address 192.168.2.3
        gateaway 192.168.2.46
        netmask 255.255.255.0
# eth0:0: ip address which heartbeat is supposed to take over
iface eth0:0 inet static
        address 192.168.2.5
        netmask 255.255.255.0

/etc/ha.d/haresources:

mx1 IPaddr::192.168.2.5
mx1 drbddisk::r0 Filesystem::/dev/drbd0::/syncdata::ext3 nfs-kernel-server

Failover works fine, but a the default gateway is lost as soon as heartbeat starts it seems (so, also after booting / not yet taking anything over). So far, the only thing I can think of is adding a route add default gw 192.168.2.46 in post-up & post-down of eth0:0, but that seems rather ugly....