[Pacemaker] Pacemaker on CentOS 5.6 & CentOS 6.0

[Andrew Beekhof]

Based on the versions, this should work.
Could you provide logs from the 4 nodes?

On Wed, Sep 7, 2011 at 10:40 PM, sdr(friedrich reichhart) <fr at sdr.at> wrote:
> Hi Andrew!
>
> CentOs 5
> ========
>
> [root at inet-storage01 ~]# yum list pacemaker corosync cluster-glue
> Loaded plugins: fastestmirror
> Loading mirror speeds from cached hostfile
>  * epel: ftp.icm.edu.pl
> Installed Packages
> cluster-glue.x86_64                                          1.0.6-1.6.el5
> installed
> corosync.i386                                                1.2.7-1.1.el5
> installed
> corosync.x86_64                                              1.2.7-1.1.el5
> installed
> pacemaker.i386                                               1.1.5-1.1.el5
> installed
> pacemaker.x86_64                                             1.1.5-1.1.el5
> installed
>
> [root at inet-storage02 ~]# yum list pacemaker corosync cluster-glue
> Loaded plugins: fastestmirror
> Loading mirror speeds from cached hostfile
>  * epel: mirror.karneval.cz
> Installed Packages
> cluster-glue.x86_64                                          1.0.6-1.6.el5
> installed
> corosync.i386                                                1.2.7-1.1.el5
> installed
> corosync.x86_64                                              1.2.7-1.1.el5
> installed
> pacemaker.i386                                               1.1.5-1.1.el5
> installed
> pacemaker.x86_64                                             1.1.5-1.1.el5
> installed
>
>
> [root at kvm02 ~]# yum list pacemaker corosync cluster-glue
> Loaded plugins: fastestmirror
> Loading mirror speeds from cached hostfile
>  * epel: mirror.fraunhofer.de
> Installed Packages
> cluster-glue.x86_64                                          1.0.6-1.6.el5
> installed
> corosync.i386                                                1.2.7-1.1.el5
> installed
> corosync.x86_64                                              1.2.7-1.1.el5
> installed
> pacemaker.i386                                               1.1.5-1.1.el5
> installed
> pacemaker.x86_64                                             1.1.5-1.1.el5
> installed
>
>
>
> CentOs 6
> =======
>
> [root at kvm04 ~]# yum list pacemaker corosync cluster-glue
> Loaded plugins: fastestmirror, presto
> Loading mirror speeds from cached hostfile
>  * base: gd.tuwien.ac.at
>  * extras: gd.tuwien.ac.at
>  * updates: gd.tuwien.ac.at
> Installed Packages
> cluster-glue.x86_64                            1.0.5-2.el6
> @base
> corosync.x86_64                                1.2.3-36.el6
> @scientific-linux
> pacemaker.x86_64                               1.1.5-5.el6
> @scientific-linux
>
>
> Thaks for help,
> Fritz.
>
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: Andrew Beekhof [mailto:andrew at beekhof.net]
>> Gesendet: Mittwoch, 07. September 2011 13:31
>> An: The Pacemaker cluster resource manager
>> Betreff: Re: [Pacemaker] Pacemaker on CentOS 5.6 & CentOS 6.0
>>
>> What are the versions of pacemaker and corosync on all nodes?
>>
>> On Sun, Sep 4, 2011 at 9:23 PM, sdr(friedrich reichhart) <fr at sdr.at>
> wrote:
>> > Hi all!
>> >
>> > I'm working in a cluster with CentOS 5 & 6
>> > Storage01 - Centos5
>> > Sotrage02 - Centos5
>> > KVM02 - Centos5
>> >
>> > This part works fine.
>> >
>> > KVM04 - Centos6
>> >
>> > [root at kvm04 ~]# /etc/init.d/corosync start && /etc/init.d/pacemaker
>> > start Starting Corosync Cluster Engine (corosync):               [  OK
>> > ] Starting Pacemaker Cluster Manager:                        [  OK  ]
>> >
>> > Both "clusters" see the other node / nodes, meaning storage01,02 +
>> > kvm02 sees node kvm02 and node kvm02 sees all other nodes.
>> >
>> > [root at kvm04 ~]# crm_mon -1
>> > ============
>> > Last updated: Sat Sep  3 09:45:26 2011
>> > Stack: openais
>> > Current DC: kvm04.sdr.at - partition WITHOUT quorum
>> > Version: 1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f
>> > 4 Nodes configured, 2 expected votes
>> > 0 Resources configured.
>> > ============
>> >
>> > Online: [ kvm04.sdr.at ]
>> > OFFLINE: [ kvm02.sdr.at inet-storage01.sdr.at inet-storage02.sdr.at ]
>> >
>> > The OFFLINE nodes were not entried manually, pacemaker found them as
>> > well as "on the other side".
>> >
>> > I'm using standard repositories + EPEL + Clusterlabs.
>> >
>> > What may be wrong?
>> > Config files, auth-file, service.d might be configured ok.
>> >
>> > Thanks for help,
>> > Fritz.
>> >
>> > _______________________________________________
>> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>> >
>> > Project Home: http://www.clusterlabs.org Getting started:
>> > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> > Bugs:
>> > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacema
>> > ker
>> >
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org Getting started:
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://developerbugs.linux-
>> foundation.org/enter_bug.cgi?product=Pacemaker
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>