[Pacemaker] target-role changing from Master to Started

Pavlos Parissis pavlos.parissis at gmail.com
Thu Nov 18 11:01:17 UTC 2010


On 18 November 2010 02:08, Rick Kint <rwkint at yahoo.com> wrote:
>
> Hello --
>
> We've experienced a weird problem 3 times in the last month on different clusters.
>
> Environment:
> - Pacemaker 1.0.9.1-1
> - Corosync 1.2.5-1
> - RHEL5.4
> - 2 nodes
>
> We run a simple configuration with a master/slave resource, appended below.
>
> Three times we have found different clusters in a state where both instances are slaves and Pacemaker seems perfectly happy with this.  Looking at the configuration (cib.xml) reveals that the target-role attribute for the master/slave resource has changed from Master to Started.  Changing the value of this attribute back to Master fixes the problem immediately.
>
> Any ideas what might be causing this?  Nobody is doing it manually.
>
> I'll hold off on logs until asked, this stuff can get voluminous.
>
>
> Thanks, Rick Kint
>
Have you checked the log? It should give some indication.

Pavlos




More information about the Pacemaker mailing list