[Pacemaker] pacemaker kills corosync

[Olivier Nicole]

Thank you Andrew,

> >> Normally pacemaker is loaded by Corosync, ie you just start corosync
> >> and leave pacemaker stopped and disabled via chkconfig. This is set
> >> in corosync.conf by this:
> >>
> >> service {
> >>         # Load the Pacemaker Cluster Resource Manager
> >>         name: pacemaker
> >>         ver:  0
> >> }
> >>
> >> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/s-configure-corosync.html
> >
> > Yes, I followed this HowTo, but it mentions that the directive service
> > {} should be in /etc/corosync/service.d/pcmk, not in
> > /etc/corosync/corosync.conf
> 
> either-or is fine
> 
> >
> > And it also mention in the note at the bootm that pacemaker is not
> > started automatically by corosync, that it will have to be started
> > later by /etc/init.d/pacemaker start in part 3.2 of the HowTo.
> 
> Only for "ver: 1", not for "ver: 0"

I am following the HowTo, so I am using "ver: 1" (I just double
check).

Everything is going exactly as described in the HowTo except one line
in the log:

Oct  6 10:07:37 cos3 corosync[1314]:   [pcmk  ] info: pcmk_startup: Service: 10

it says Service: 9 in the HowTo.

And when I follow the next step, that is start pacemaker, the problem
appears.

I don't have the lines:

Feb  8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14022 for process stonith-ng
Feb  8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14023 for process cib

in the log. ps axf does not show the processes cib, lrmd, etc.

And I notice that the process corosync is dead.

TIA,

Olivier




> 
> >
> > Thank you,
> >
> > Olivier
> >
> >> Do you have this set?
> >> Max
> >>
> >> -----Original Message-----
> >> From: Olivier Nicole [mailto:Olivier.Nicole at cs.ait.ac.th]
> >> Sent: 05 October 2011 12:11
> >> To: Pacemaker at oss.clusterlabs.org
> >> Subject: [Pacemaker] pacemaker kills corosync
> >>
> >> Hi,
> >>
> >> I am new to pacemaker. I want to set-up a small cluter to provide high availability for NFS. The disk sharing is taken care off.
> >>
> >> I am trying to figure out how to configure/run corosync and pacemaker.
> >>
> >> My test plateform is CentOS 6.0, with pacemaker installed from the packages.
> >>
> >> [root at cos3 log]# pacemakerd --version
> >> Pacemaker 1.1.2
> >> Written by Andrew Beekhof
> >> [root at cos3 log]# corosync -v
> >> Corosync Cluster Engine, version '1.2.3' SVN revision 'exported'
> >> Copyright (c) 2006-2009 Red Hat, Inc.
> >>
> >> It seems that corosync is working fine, but whenever I try to start pacemakerd, the corosync process dies and I get nothing in any log.
> >>
> >> I am completely lost.