On 11 October 2010 11:12, Pavlos Parissis <pavlos.paris...@gmail.com> wrote: > Hi, > > Cluster got an error on monitor and stop action on a resource and > since then I can't do stop/start/manage/unmanage that resource. > For some strange reason the actions monitor/stop failed, manually > worked, but i can't figure out why they failed when cluster run status > and stop on the specific lsb resource. > > The issue now is that I can't do anything about that resource, even I > have cleared out the failcount counter. > > How can i escape from the situation? > > hb_report attached > > Regards, > Pavlos >
After reading again and again the "configuration explained" document and especial page 18, I found a solution. Adding on-fail="stop" for monitor/stop/start operation on the resource get me out that situation. After I added this setting cluster initiated stop action which was successful.! The resource was stuck, actually blocked, because that is the default action when stop action fails and stonith is disabled. Blame on me not remembering page 18:-) Cheers, Pavlos _______________________________________________ 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
