Il giorno Lun 17 Mag 2010 10:04:22 CET, Andrew Beekhof ha scritto:
> On Mon, May 17, 2010 at 9:46 AM, RaSca<[email protected]> wrote:
>> What should else can i check?
> logs, cibadmin output.
> the usual stuff
Hi Andrew,
i think I found something interesting. If i remove this location:
location store_on_connected_node store \
rule $id="store_on_connected_node-rule" -inf: not_defined pingd
or pingd lte 0
then the resources comes up correctly at boot time. I tried this after
reading the logs as you said:
WARN: native_color: Resource pingd:1 cannot run anywhere
was the first harming thing, and then:
info: native_merge_weights: store-vg_drbd: Rolling back scores from
<RESOURCE NAME>
It seems like if pingd, which for me is a cloned resource, does not
start on both nodes, then the weight of the other resource is put on
-inf. And in a way this is correct, because the location say this. What
I don't understand is that in the first node, the status of the pingd
resource is "started" even if the first time it "cannot run anywhere".
So, what am I missing?
Thanks for your help,
--
RaSca
Mia Mamma Usa Linux: Niente รจ impossibile da capire, se lo spieghi bene!
[email protected]
http://www.miamammausalinux.org
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
