On Wed, Dec 10, 2008 at 15:11, Tim Verhoeven <[EMAIL PROTECTED]> wrote: > Hi, > > I've got another issue with clones. As you can see in the attached > cib.xml. As you can see the clone_ip200 resource has a clone_max and > clone_node_max set to 2. crm_verify is reporting no errors or > warnings. But the cluster will not start 2 clones on the same machine. > This is the output from crm_mon -1 :
yeah, that looks wrong. can you attach the full cib "cibadmin -Q" when the cluster is in this state? > > Clone Set: clone_named1 > resource_named1:0 (ocf::dns:named): Started slave1 > resource_named1:1 (ocf::dns:named): Stopped > Clone Set: clone_ip200 > resource_ip200:0 (ocf::heartbeat:IPaddr2): Started slave1 > resource_ip200:1 (ocf::heartbeat:IPaddr2): Stopped > > I see this in the logs : > > slave1 pengine: [3552]: WARN: native_color: Resource resource_ip200:1 > cannot run anywhere > > As you can see I don't have any constraints so it should start the 2 > clones. This was all working fine on a Heartbeat 2.1/Pacemaker 0.6 > cluster. I'm currently testing this with pacemaker-1.0.1-3.1 and > heartbeat-2.99.2-6.1. > > Any ideas ? > > Thanks, > Tim > > -- > Tim Verhoeven - [EMAIL PROTECTED] - 0479 / 88 11 83 > > Hoping the problem magically goes away by ignoring it is the > "microsoft approach to programming" and should never be allowed. > (Linus Torvalds) > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
