[Linux-HA] pacemaker virtual ip does not start (was: Unknown Problems with Heartbeat)
lars.ellenberg at linbit.com
Fri Jan 20 11:26:14 MST 2012
On Thu, Jan 12, 2012 at 12:29:18PM +0100, Niclas Müller wrote:
> Hey Guys,
> I'm currently going to setup a Linux HA Cluster with apache and MySQL.
> I've created three VM with KVM Vitalization. One NetworkManager as DNS
> and DHCP Server, and two other as Cluster Nodes. All VMs are both Debian
> Squeeze minimal installations. On the Nodes i've installed the packages
> heartbeat and pacemaker. The configuration of heartbeat seems like
> correct because in the syslog there are no errors and i can read that
> the nodes have contact. My first impression of the software packages is,
> that heartbeat is only for checking the Nodes of ability. Pacemaker is
> for the services which are to manager. I cannot get it on that heartbeat
> / pacemaker (??) use the virtual ip. In both interfaces there is no
> eth0:0 with the configurated ip address. Is the virtual ip used by the
> primary node only when a service is confiugrated? Have anybody a good
> howto for set up a apache and mysql cluster with heartbeat and pacemaker
You could not come up with a less descriptive subject ;)
This may be just the ip vs ifconfig non-issue again,
I suspect your IP does start, it only does not show up
in ifconfig output.
IPaddr != IPaddr2, the former works with ifconfig,
and creates "named alias interfaces", which are
labeled secondary addresses on the base NIC,
to use the terms of iproute2.
The latter works with ip (from the iproute2 package),
and by default does NOT label the secondary addresses it creates.
Unlabeled secondary addresses do not show up in ifconfig -a.
To see them, you'd need to use "ip addr show" (my favorite variant being
ip -o -f inet a s).
You can also add the "iflabel=xyz" parameter to the IPaddr2 primitive,
to get what you probably expect.
There is no other difference between labeled and unlabeled addresses.
BTW, labels do not need to be 0,1,2: you can also use the label "web" or
"mail" or "vinotinto". They are limited in length, though.
The length over "<devicename>:label" has to be <= 15 bytes
(IFNAMSIZ - terminating NUL).
Which means eth0:vinotinto works, but eth0:cabernetsauvignon will fail
with the non-obvious "RTNETLINK answers: Numerical result out of range".
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
More information about the Linux-HA