On Fri, Nov 12, 2010 at 10:47 AM, Vadim S. Khondar <v.khon...@o3.ua> wrote: > У ср, 2010-11-10 у 09:03 +0100, Andrew Beekhof пише: >> On Tue, Nov 9, 2010 at 2:14 PM, Vadim S. Khondar <v.khon...@o3.ua> wrote: >> > У вт, 2010-11-09 у 09:49 +0100, Andrew Beekhof пише: >> >> being unmanaged is a side-effect of a) the resource failing to stop >> >> and b) no fencing being configured >> >> once you've fixed the error, run crm resource cleanup as misch suggested >> >> >> > >> > I understand that. >> > However, for example, in situation when VPS fails to start (not to stop) >> >> Its failing to stop too: >> >> ca_stop_0 (node=ha-3, call=49, rc=1, status=complete): unknown error >> ^^^^^^^^ > >> >> Possibly an ordering constraint. Otherwise, no idea. >> Depends on how your resource agent works. > > No ordering constraints explicitly listed in configuration.
Right, I'm suggesting that might be the problem. > :( > > Will try with moving to v1.1. > > -- > Vadim S. Khondar > > v.khon...@o3.ua > > _______________________________________________ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
