Re: Heartbeat Error

To: " users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Heartbeat Error
From: Horms <horms@xxxxxxxxxxxx>
Date: Fri, 30 Jun 2006 16:15:29 +0900 (JST)
In article <ECB273EEB21CC8449E62CC1F974D37C44ED329@xxxxxxxxxxxxxxxxxxxxxx> you 
> When starting up heartbeat (service heartbeat start) on FC5 system I
> get:
> [root@SBLB-Master ~]# service heartbeat start
> logd is already running
> Starting High-Availability services:
> eth0:0: warning: name may be invalid
> 2006/06/29_09:54:22 INFO: IPaddr2 Resource is stopped
>                                                           [FAILED]
> heartbeat[7642]: 2006/06/29_09:54:22 ERROR: glib: Get broadcast for
> interface eth1 failed: Cannot assign requested address
> heartbeat[7642]: 2006/06/29_09:54:22 ERROR: glib: IP interface [eth1]
> does not exist
> heartbeat[7642]: 2006/06/29_09:54:22 ERROR: Illegal bcast [UDP/IP
> broadcast] in config file [eth1]
> heartbeat[7642]: 2006/06/29_09:54:22 ERROR: Heartbeat not started:
> configuration error.
> heartbeat[7642]: 2006/06/29_09:54:22 ERROR: Configuration error,
> heartbeat not started.
> What am I missing?

IPaddr tries to work out the broadcast address (and other information)
based on existing interface configurations on your system (not a good
idea IMHO). I suspect that what is happening is that you do not
have an interface set up on the same network (for some value of network)
as the VIP, and thus this error.

This is easy to get around by just fully specifying the address which
you want to use (which I strongly recommend doing always).
Something like this should work:


The format is:

Where prefix is the number of bits in the netmask, 24 is

H:          W:

<Prev in Thread] Current Thread [Next in Thread>