[Pacemaker] Pacemaker restart resources when node joins cluster after failback

José Alonso jah at transtelco.net
Tue Mar 6 00:38:26 EST 2012

Hi all,

I removed apache from the init-process but still having the same behavior.
When a node rejoins the cluster, all resources are restarted again. Is
there any way to avoid that??

Best regards,


On Mon, Mar 5, 2012 at 2:53 PM, Arnold Krille <arnold at arnoldarts.de> wrote:

> Hi,
> On Monday 05 March 2012 12:58:16 José Alonso wrote:
> > I have 2 Debian nodes with heartbeat and pacemaker 1.1.6 installed, and
> > almost everything is working fine, I have only apache configured for
> > testing, when a node goes down the failover is done correctly, but
> there's
> > a problem when a node failbacks.
> >
> > For example, let's say that Node1 has the lead on apache resource, then I
> > reboot Node1, so Pacemaker detect it goes down, then apache is promoted
> to
> > the Node2 and it keeps there running fine, that's fine, but when Node1
> > recovers and joins the cluster again, apache is restarted on Node2 again.
> >
> > Anyone knows, why resources are restarted when a node rejoins a cluster ?
> Just a quick guess: Your node1 is starting apache from the init-process,
> pacemaker detects that. Since running two instances is not what pacemaker
> wants, it stops all of them and restarts the one it wants to see up.
> Have fun,
> Arnold
> _______________________________________________
> 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 --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120305/af6e97fc/attachment-0003.html>

More information about the Pacemaker mailing list