On 18 November 2010 02:08, Rick Kint <rwk...@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 _______________________________________________ Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
