pingd is a daemon with is running all the time and does it job<br>you still need to define monitor operation though, what if the daemon dies?<br>op monitor just have a different meaning for ping and pingd.<br>with pingd - monitor daemon<br>
with ping - monitor connectivity<br><br>as for warnings:<br><br>crm configure property default-action-timeout="120s"<br><br><div class="gmail_quote">On Tue, May 11, 2010 at 11:00 AM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com">gianluca.cecchi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im"><div class="gmail_quote">On Tue, May 11, 2010 at 1:13 PM, Vadym Chepkov <span dir="ltr"><<a href="mailto:vchepkov@gmail.com" target="_blank">vchepkov@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); 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><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>
<br>_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br></blockquote></div><br>