[Pacemaker] first monitor action after start of ressource fails - ends up in ressource restart

Andrew Beekhof andrew at beekhof.net
Tue Jun 17 19:07:03 EDT 2014

On 17 Jun 2014, at 4:21 pm, Bauer, Stefan (IZLBW Extern) <Stefan.Bauer at iz.bwl.de> wrote:

> Dear Users/Developers,
> I’m running a pacemaker/corosync cluster on Debian 7:
> Pacemaker
> Corosync 1.4.2-3
> Everything is smooth but the first monitor action after the start action on my apache2 ressource fails – hence it ends up in a restart.
> How can this be avoided?

Sounds like apache is saying "done" for the start action before its actually started.
I believe more recent versions of the agent behave correctly.

> Log attached.
> Thanks
> Stefan
> <apache-debug.txt.txt>_______________________________________________
> 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: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140618/fa25aebd/attachment-0003.sig>

More information about the Pacemaker mailing list