[Pacemaker] pacemaker shutdown issue after OS change

Andrew Beekhof andrew at beekhof.net
Sun Feb 16 20:30:38 EST 2014

On 31 Jan 2014, at 3:18 am, Pascal BERTON <pascal.berton3 at free.fr> wrote:

> Hi !
> I recently changed hosting platform versions for my PCMK clusters, from RHEL6.0 equivalent towards SL6.4. Also changed from pcmk 1.1.2+corosync 1.3.3  to pcmk 1.1.10+corosync 1.4.1 that come with SL6.
> Until now, I used to manage my pcmk+corosync layers directly from my own personal init scripts, so I used to globaly disable pacemaker using chkconfig. It was my scripts duty to start up cluster layer at boot and stop it at node shutdown. And it has all worked fine for a couple of years !
> With that new platform, I now see something odd at node shutdown : Although both pacemaker and corosync services are disabled for every runlevel (And BTW if I disable my own service, they won’t start at boot), I can see that pacemaker’s init script is called as soon as I run the shutdown –r command.
> After digging into what’s happening inside, I can clearly see that although disabled, pacemaker is still called immediately, does its job of stopping the cluster and the related resources, and then when my own script runs (1st in the shutdown script list) and tries to interract with the cluster layer, too late, it has already died and its actions are not managed correctly.
> I can workaround that by integrating my own shutdown sequence directly within pacemaker init script, but I‘d prefer making things cleaner by maintaining them separate.
> Is this behavior something expected


> (Or is it me ? ‘Wouldn’t be the first time… J )? What launches that disabled script ? Can I change that ?

Very good question.
It could be chkconfig doing something "smart" with the LSB metadata:

# Default-Start:  2 3 4 5
# Default-Stop:   0 1 6

There was a subsequent commit to replace that with:

# Default-Start:
# Default-Stop:

which may help as may running:

/sbin/chkconfig --del pacemaker

instead of

/sbin/chkconfig pacemaker off

> Thanks for your help !
> Regards,
> Pascal.
> Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection Antivirus avast! est active.
> _______________________________________________
> 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://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140217/c7620f2d/attachment-0002.sig>

More information about the Pacemaker mailing list