[ClusterLabs] A processor failed, forming new configuration very often and without reason

Andrew Beekhof andrew at beekhof.net
Sun Apr 12 23:00:42 EDT 2015

> On 10 Apr 2015, at 11:37 pm, Philippe Carbonnier <Philippe.Carbonnier at vif.fr> wrote:
> Hello,
> The context : 
>   Red Hat Enterprise Linux Server release 5.7
>   corosynclib-1.2.7-1.1.el5.x86_64
>   corosync-1.2.7-1.1.el5.x86_64
>   pacemaker-1.0.10-1.4.el5.x86_64
>   pacemaker-libs-1.0.10-1.4.el5.x86_64
>   2 nodes, both on same ESX server
> I've lost of processor joined of left the membership message but can't understand why, because the 2 hosts are up and running, and when the corosync try to start the cluster's ressource he can't because the are already up on the first node. 
> We can see "Another DC detected" so the communication between the 2 VM is OK.
> I've tried to raise totem parameter, without success.

> Apr 10 13:34:55 host2.example.com pengine: [26529]: WARN: unpack_rsc_op: Processing failed op routing-jboss_stop_0 on tango2.luxlait.lan: invalid parameter (2)

^^^ Failed stops lead to fencing.

The agent and/or your config need fixing.

More information about the Users mailing list