On 11/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a problem with migrating resources. The config is the same as
> with my earlier postings:
>
> I started my 3 nodes with 3 groups, group 1 defaults to node 1 and so on.
> Due to a previous (known) problem during shutdown, the db2 resources did
> not start on the first attempt. So I ended up with resources of group 3
> running on node 2 - fine. At that point I started crm_resource to
> migrate group 3 to node 3. This failed. The resources where stopped on
> node 2 but not started on group 3.
>
> Can it be, that the cluster remembers earlier failures of group 3 on
> node 3 and thus refuses to start them there again?

yes - this is exactly what it does

>
> How do I get rid of that restriction?

once you have fixed whatever the problem was on node 3, you can use:
   crm_resource -C -H node3 -r name_of_the_resource_that_failed_there

>
> I'm sorry to say, that currently I cannot provide the logs and cannot
> reproduce the problem. Only some output I saved from the terminals. But
> if the given infos do not suffice, I'll try harder...
>
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Reply via email to