On 8/13/07, James Oakley <[EMAIL PROTECTED]> wrote:
> I am having some trouble getting resources to failover in my 2.1.2 2-node
> cluster.
>
> I have attached my cib.
>
> I created a number of resources and colocation rules. All of the resources
> need to run on the same node that has the drbd partition mounted.
>
> If I kill the daemon process of one of the dependent resources, it is simply
> restarted, which is good. Unfortunately, if I make the failure more severe by
> renaming the daemon binary and then killing it, heartbeat simply calls the
> stop action and leaves it at that. It doesn't bother migrating the resources
> to the other node.
>
> I understand that if all of the resources were in a group, the whole group
> would failover, but that also means that if one resource in the group failed
> on both nodes, the whole group would be shut down, and I *definitely* don't
> want that.
>
> Also, if a resource fails and I later fix the problem, I can't seem to get
> heartbeat to take it over again. I tried "crm_failcount -G -r <resource>" and
> starting the process manually, then calling "crm_resource -P -H <node> -r
> <resource>", but crm_mon still shows "(unmanaged) FAILED." The only thing
> that works is stopping and restarting heartbeat on both nodes.

I'm guessing that the resource failed to stop
And since stonith is not enabled there is nothing we can do (since
it's not safe to start it somewhere else while its still, potentially,
active on the first node).

But thats just a guess since you didn't include logs or the complete CIB
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to