<div>On Tue, May 11, 2010 at 12:50 PM, Vadym Chepkov <span dir="ltr"><<a href="mailto:vchepkov@gmail.com">vchepkov@gmail.com</a>></span> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">You forgot to turn on monitor operation for ping (actual job)<div><div><br></div><div><br></div></div></div></blockquote></div><div><div><br></div><div>I saw from the </div><div><div>[root@ha1 ~]# crm ra meta ping </div>
</div><div>command</div><div><br></div><div>Operations' defaults (advisory minimum):</div><div><br></div><div> start timeout=60</div><div> stop timeout=20</div><div> reload timeout=100</div>
<div> monitor_0 interval=10 timeout=60</div></div><div><br></div><div>So I presumed it was by default in place for the ping resource.....</div><div>Do you mean that I should define the resource this way:</div><div>
<div>crm configure primitive pinggw ocf:pacemaker:ping \</div><div>> params host_list="192.168.101.1" multiplier="100" \</div><div>> op start interval="0" timeout="90" \</div>
<div>> op stop interval="0" timeout="100" \</div></div><div>> op monitor interval=10 timeout=60</div><div><br></div><div>Ok, I did it and I now get the same behavior as with pingd. Thanks ;-)</div>
<div><br></div><div><div>Migration summary:</div><div>* Node ha1: pingd=0</div><div>* Node ha2: pingd=100</div></div><div><br></div><div>And if I remove the iptables rule I get:</div><div><div>Migration summary:</div><div>
* Node ha1: pingd=100</div><div>* Node ha2: pingd=100</div></div><div><br></div><div>Now I will check the "all resources stopped" problem...</div>