<div class="gmail_quote">On Tue, May 11, 2010 at 1:13 PM, Vadym Chepkov <span dir="ltr"><<a href="mailto:vchepkov@gmail.com">vchepkov@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">First of all, none of the monitor operation is on by default in pacemaker, this is something that you have to turn on<div>For the ping RA start and stop op parameters don't do much, so you can safely drop them.<br>
<div><br><div><br></div></div></div></div></blockquote></div><div><br></div><div>Yes, but for the pacemaker:pingd RA I didn't need to pass the "op monitor" parameter to have it working....</div><div> </div><div>
Also, in general I added the start/stop op parameters, because without them I get, for example with the command you suggested:</div><div><br></div><div><div>[root@ha1 ~]# crm configure primitive pinggw ocf:pacemaker:ping \</div>
<div>> params host_list="192.168.101.1" multiplier="200" timeout="3" \</div><div>> op monitor interval="10"</div><div>WARNING: pinggw: default-action-timeout 20s for start is smaller than the advised 60</div>
<div>WARNING: pinggw: default-action-timeout 20s for monitor_0 is smaller than the advised 60</div></div><div><br></div><div>Do I have to ignore the warnings?</div><div>Or do I have to adapt the resource creation with:</div>
<div><div>[root@ha1 ~]# crm configure primitive pinggw ocf:pacemaker:ping \</div><div>> params host_list="192.168.101.1" multiplier="200" timeout="3" \</div><div>> op start timeout="60"</div>
</div><div><br></div><div>That gives no warnings (even if I would have expected the warning about the monitor_0 timeout as I didn't set it...???)</div><div><br></div><div><br></div><div><br></div>