[Pacemaker] "ERROR: Wrong stack o2cb" when trying to start o2cb service in Pacemaker cluster

[David Guyot]

Hello!

No, I didn't solved my problem; instead, I removed the non-essential
OCFS2 functionality from my cluster. Nevertheless, from what I remember,
this likely comes from a bug, so your answer seems consistent.

It could prove helpful in the future.

Thank you!

Kind regards.

Le 26/07/2012 14:39, Bruno MACADRE a écrit :
> Hi,
>
>     I don't known if you solved your problem but I just have the same
> behavior on my fresh installed pacemaker.
>
>     With the 2 lines :
> p_o2cb:1_monitor_0 (node=nas1, call=10, rc=5,status=complete): not
> installed
> p_o2cb:0_monitor_0 (node=nas2, call=10, rc=5, status=complete): not
> installed
>
>     After some tries, I've found a bug in the resource agent
> ocf:pacemaker:o2cb
>
>     When this agent start, his first action is to do a 'o2cb_monitor'
> to check if o2cb is already started. If not (ie $? ==
> $OCF_NOT_RUNNING) it load all needed adn finally start.
>
>     The bug is that 'o2cb_monitor' return $OCF_NOT_RUNNING if
> something is missing, except for the module 'ocfs2_user_stack' which
> he returns $OCF_ERR_INSTALLED. So if the module 'ocfs2_user_stack' is
> not loaded before starting ocf:pacemaker:o2cb resource agent it fails
> to start with 'not installed' error.
>
>     The workaround I've just find is to place 'ocfs2_user_stack' in my
> /etc/modules on all nodes and all works fine.
>
>     I hope I helped someone and this bug was corrected in future
> release of o2cb RA.
>
> For information :
>     . OS : Ubuntu Server 12.04 x64
>     . Pacemaker : 1.1.6
>     . Stack : cman 3.1.7
>
>     Regards,
>     Bruno
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 554 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120726/03c55459/attachment-0003.sig>