On Tue, Feb 23, 2010 at 3:32 PM, Alain.Moulle <alain.mou...@bull.net> wrote: > Hi Andrew > > ok that was not a good choice to take smard as test init script to > demonstrate the problem about group ... sorry , so I did some simple > scripts /pingalain1/ (resource respingal1) and /pingalain2/ (resource > respingal2) > which have for sure status eq 0 gathered in a group /groupresping/ : > crm configure group groupresping respingal1 respingal2 and so my problem is > that : > > 1/ when both respingal1 and respingal2 are successfully started/running, > if I stop respingal1, both resources are stopped. (Fine for me) > 2/ when both respingal1 and respingal2 are successfully started/running, > if I stop respingal2, there is no impact on respingal1. (Not fine for me > ...)
stopped how? with target-role or by killing the actual service? > > As I told you, it seemed to be the behavior described p28 of your > documentation > but you told me in previous email, if I well understood, that it should no > more be > the behavior, and both resources should be stopped , whatever the one we > chose to stop. > > Joined is the new cibadmin-Ql just after the case 2 > > Thanks > Regards > Alain >> >> smartd2 can't run on node1 because it returned rc=5 for the monitor op. >> >> EXECRA_NOT_INSTALLED = 5, >> >> >> On Mon, Feb 22, 2010 at 3:34 PM, Alain.Moulle <alain.mou...@bull.net> >> wrote: >> >>> >>> > Hi Andrew, >>> > >>> > sorry for the delay, but about my problem on groups I've reproduced ?it >>> > with >>> > only two resources resal1 and resal2 gathered in a group groupal1. >>> > The behavior is : >>> > >>> > 1/ when both res are started, and I stop resal1 , all the group is >>> > stopped. >>> > 2/ when both res are started, and I stop resal2 , there is no impact on >>> > resal1 >>> > ? crm_mon gives : >>> > ? ?Resource Group: groupal1 >>> > ? ?resal1 ? ? (lsb:smartd): ? Started node1 >>> > ? ?resal2 ? ? (lsb:smartd2): ?Stopped >>> > >>> > Joined is the cibadmin -Ql after the 1/ >>> > >>> > Thanks >>> > Regards >>> > Alain >>> > >>> >>>> >>>> >> Hi Andrew, >>>> >>>>> >>>>> >> > the releases are those officially delivered with fc12 : >>>>> >> > pacemaker-1.0.5-4.fc12 >>>>> >> > and : >>>>> >> > cluster-glue-1.0-0.11.b79635605337.hg.fc12 >>>>> >> > corosync-1.1.2-1.fc12 >>>>> >> > heartbeat-3.0.0-0.5.0daab7da36a8.hg.fc12 >>>>> >> > openais-1.1.0-1.fc12 >>>>> >> > all in x86_64 . >>>>> >> > >>>>> >>>> >>>> >> >>>> >> When the cluster is in that state (4th resource stopped) can you run >>>> >> cibadmin -Ql and attach the result? > > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
