[Pacemaker] Pacemaker cluster with different operating systems

Thu Mar 7 07:01:38 UTC 2013

Hi Andrew,
Yes, I added "pcmk" file under "/etc/corosync/service.d/" folder.
Since you think the setup should work, here are the details of the problem.
Could you please check for any problem? I hope I have given enough information about the setup and problem.

[root at pmidea1 ~]# more /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.2 (Santiago)
[root at pmidea1 ~]# rpm -qa|egrep "corosync|pacemaker"
pacemaker-libs-1.1.8-4.el6.x86_64
corosync-1.4.3-26.2.x86_64
pacemaker-cluster-libs-1.1.8-4.el6.x86_64
corosynclib-1.4.3-26.2.x86_64
pacemaker-cli-1.1.8-4.el6.x86_64
pacemaker-1.1.8-4.el6.x86_64
[root at pmidea1 ~]# more /etc/corosync/service.d/pcmk 
service {
      name: pacemaker
      ver: 1
}

[root at pmidea2 ~]# more /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.2 (Santiago)
[root at pmidea2 ~]# rpm -qa|egrep "corosync|pacemaker"
pacemaker-libs-1.1.8-4.el6.x86_64
corosync-1.4.3-26.2.x86_64
pacemaker-cluster-libs-1.1.8-4.el6.x86_64
corosynclib-1.4.3-26.2.x86_64
pacemaker-cli-1.1.8-4.el6.x86_64
pacemaker-1.1.8-4.el6.x86_64
[root at pmidea2 ~]# more /etc/corosync/service.d/pcmk 
service {
      name: pacemaker
      ver: 1
}

[root at pmosidea ~]# more /etc/redhat-release 
Red Hat Enterprise Linux Server release 5.5 (Tikanga)
[root at pmosidea ~]# rpm -qa|egrep "corosync|pacemaker"
pacemaker-cluster-libs-1.1.8-2.el5
corosynclib-1.4.1-7.el5.1
pacemaker-1.1.8-2.el5
corosync-1.4.1-7.el5.1
pacemaker-cli-1.1.8-2.el5
pacemaker-libs-1.1.8-2.el5
[root at pmosidea ~]# more /etc/corosync/service.d/pcmk 
service {
      name: pacemaker
      ver: 1
}

Corosync membership:
--------------------
[root at pmidea1 ~]# corosync-objctl | grep member
totem.interface.member.memberaddr=10.34.38.46
totem.interface.member.memberaddr=10.34.38.47
totem.interface.member.memberaddr=10.34.38.48
runtime.totem.pg.mrp.srp.members.791028234.ip=r(0) ip(10.34.38.47) 
runtime.totem.pg.mrp.srp.members.791028234.join_count=1
runtime.totem.pg.mrp.srp.members.791028234.status=joined
runtime.totem.pg.mrp.srp.members.774251018.ip=r(0) ip(10.34.38.46) 
runtime.totem.pg.mrp.srp.members.774251018.join_count=1
runtime.totem.pg.mrp.srp.members.774251018.status=joined
runtime.totem.pg.mrp.srp.members.807805450.ip=r(0) ip(10.34.38.48) 
runtime.totem.pg.mrp.srp.members.807805450.join_count=1
runtime.totem.pg.mrp.srp.members.807805450.status=joined

[root at pmosidea ~]# corosync-objctl | grep member
totem.interface.member.memberaddr=10.34.38.46
totem.interface.member.memberaddr=10.34.38.47
totem.interface.member.memberaddr=10.34.38.48
runtime.totem.pg.mrp.srp.members.774251018.ip=r(0) ip(10.34.38.46) 
runtime.totem.pg.mrp.srp.members.774251018.join_count=1
runtime.totem.pg.mrp.srp.members.774251018.status=joined
runtime.totem.pg.mrp.srp.members.791028234.ip=r(0) ip(10.34.38.47) 
runtime.totem.pg.mrp.srp.members.791028234.join_count=1
runtime.totem.pg.mrp.srp.members.791028234.status=joined
runtime.totem.pg.mrp.srp.members.807805450.ip=r(0) ip(10.34.38.48) 
runtime.totem.pg.mrp.srp.members.807805450.join_count=1
runtime.totem.pg.mrp.srp.members.807805450.status=joined

crm_mon outputs:
----------------
>From pmidea1:
-------------
Last updated: Thu Mar  7 08:53:25 2013
Last change: Thu Mar  7 02:47:51 2013 via crmd on pmidea2
Stack: openais
Current DC: pmidea2 - partition with quorum
Version: 1.1.8-4.el6-394e906
3 Nodes configured, 2 expected votes
0 Resources configured.

Online: [ pmidea1 pmidea2 ]
OFFLINE: [ pmosidea ]

>From pmosidea:
--------------
Last updated: Thu Mar  7 08:53:21 2013
Last change: Thu Mar  7 03:16:50 2013 via crmd on pmosidea
Stack: openais
Current DC: pmosidea - partition WITHOUT quorum
Version: 1.1.8-2.el5-394e906
3 Nodes configured, 2 expected votes
0 Resources configured.

Node pmidea1: pending
Node pmidea2: pending
Online: [ pmosidea ]

-----Original Message-----
From: pacemaker-request at oss.clusterlabs.org [mailto:pacemaker-request at oss.clusterlabs.org] 
Sent: 07 Mart 2013 Perşembe 08:02
To: pacemaker at oss.clusterlabs.org
Subject: Pacemaker Digest, Vol 64, Issue 30

------------------------------

Message: 2
Date: Thu, 7 Mar 2013 16:36:17 +1100
From: Andrew Beekhof <andrew at beekhof.net>
To: The Pacemaker cluster resource manager
	<pacemaker at oss.clusterlabs.org>
Subject: Re: [Pacemaker] Pacemaker cluster with different operating
	systems
Message-ID:
	<CAEDLWG2cLNUax9ANhJ2xvzdhN6sk8SteUGw0vB0E-VT1EQnLbg at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Mar 7, 2013 at 4:09 PM, Osman Findik <Osman.Findik at telenity.com> wrote:
> Hi all,
> We are using pacemaker with RHEL 6.2 successfully to manage pair of 
> MySQL databases. Pacemaker is coming from Red Hat High Availability Add-on. Its version is 1.1.6 Our need is to add an observer to this cluster but our existing servers are all RHEL 5.x servers. We could not locate same version of pacemaker in clusterlabs repo.
> So we tried to install provided rpms from clusterlabs repo to RHEL 5.5 and RHEL 6.2 servers.
> Provided rpm version for RHEL 5 is pacemaker 1.1.8.2.
> Provided rpm version for RHEL 6 is pacemaker 1.1.8.4.
>
> In this setup although servers are members of the cluster over corosync, they could not see each other from pacemaker.
> I also tried to install 1.1.8.1 rpm packages in order to use same pacemaker releases, but that is also failed.
>
> Before giving details of the errors, my question is do you think a hybrid setup with different OSs (RHEL 5.x and RHEL 6.x) is possible?

It should be.
You're using the pacemaker plugin for corosync?

------------------------------