On 2013-10-10T14:41:49, Lev Sidorenko <l...@securemedia.co.nz> wrote:
> When I create resource like:
> # pcs resource create myres lsb:myres
> it is created and can see straight away in crm_mon:
> ---------------------------------
> myres (lsb:myres): Started node3 (unmanaged) FAILED
> Failed actions:
> myres_stop_0 (node=node3, call=34, rc=5, status=complete): not
> installed
> ---------------------------------
>
> Of course it failed because myres does not exists on node3
> The behaviour the same even node3 in a standby mode!
>
> So, why cluster trying to run myres on node3 and how to prevent that?
It's not trying to run it there. It's trying to *stop* it there. That
very likely means that a "monitor" (LSB: "status") found the resource to
be active (or at least not cleanly stopped).
So pacemaker tried to correct for that and make sure the node is really
in "standby" mode.
The fix is to not have resources active where they shouldn't be; or if
scripts report the wrong status, to fix that.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
