On 2013-09-05T12:23:23, Andreas Mock <andreas.m...@web.de> wrote:
> - resource monitoring failed on node 1
> => stop of resource on node 1 failed
> => stonith off node 1 worked
> - more or less parallel as resource is clone resource
> resource monitoring failed on node 2
> => stop of resource on node 2 failed
> => stonith of node 2 failed as stonith resource agent on
> node 1 is unreachable caused by stonithing of node1
>
> - Error message stating, giving up stonithing.
> => node 2 in the state above
>
> Interestingly: a "service stop pacemaker" doesn't work
> as pacemaker seems to be blocked by this node state.
>
> The questions:
> 1) How to recover from this state without rebooting?
A cleanup on the failed resource(s) (after fixing the problem with them,
that is) should do it.
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
