[Pacemaker] questions about expected behaviour stonith:meatware

Dejan Muhamedagic dejanmm at fastmail.fm
Wed Jun 15 21:14:49 UTC 2011


Hi,

On Wed, Jun 15, 2011 at 10:29:15PM +0200, Jelle de Jong wrote:
> Hello everybody,
> 
> I was doing some testing/experiments with stonith:meatware using the
> following configuration: http://paste.debian.net/119991/
> 
> question 1: does somebody know if I should add a pingd location to the
> meatware stonith (see configuration)

No.

> question 2: I had my resources running on node hennessy, pulled out all
> network cables to see what happens next...
> 
> The viktoriya node detects hennessy is gone and sends out the following
> distress call:
> 
> info: client tengine [pid: 1776] requests a STONITH operation RESET on
> node hennessy
> info: stonith_operate_locally::2713: sending fencing op RESET for
> hennessy to stonith_hennessy (meatware) (pid=8029)
> CRIT: OPERATOR INTERVENTION REQUIRED to reset hennessy.
> CRIT: Run "meatclient -c hennessy" AFTER power-cycling the machine.
> 
> So I am waiting and waiting until viktoriya starts its kvm guests but
> nothing happens it just sits there... http://paste.debian.net/119984/
> 
> _until_ I executed meatclient -c hennessy (y) and the kvm guests started
> 
> Is this what stonith:meatware is expected to do? I was hoping viktoriya

Yes. meatware is software run by meat (aka operator). It says so
above:

	OPERATOR INTERVENTION REQUIRED to reset hennessy.

Funny but it looks fairly unequivocal to me.

Basically, a human has to make sure that the node is down and
harmless and then to run meatclient.

Thanks,

Dejan


> would start the kvm guests, sent out distress and will fence hennessy
> and expect the administrator to get hennessy back in a usable state and
> then execute the meatclient -c hennessy command so AFTER a reboot.
> 
> The only documentation I could find:
> less -S /usr/share/doc/cluster-glue/stonith/README.meatware
> 
> Thanks in advance,
> 
> Kind regards,
> 
> Jelle de Jong
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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




More information about the Pacemaker mailing list