[Pacemaker] clone ip definition and location stops my resources...

[Gianluca Cecchi]

On Tue, May 11, 2010 at 1:13 PM, Vadym Chepkov <vchepkov at gmail.com> wrote:

> First of all, none of the monitor operation is on by default in pacemaker,
> this is something that you have to turn on
> For the ping RA  start and stop op parameters don't do much, so you can
> safely drop them.
>
>
>
Yes, but for the pacemaker:pingd RA I didn't need to pass the "op monitor"
parameter to have it working....

Also, in general I added the start/stop op parameters, because without them
I get, for example with the command you suggested:

[root at ha1 ~]# crm configure primitive pinggw ocf:pacemaker:ping \
> params host_list="192.168.101.1" multiplier="200" timeout="3" \
> op monitor interval="10"
WARNING: pinggw: default-action-timeout 20s for start is smaller than the
advised 60
WARNING: pinggw: default-action-timeout 20s for monitor_0 is smaller than
the advised 60

Do I have to ignore the warnings?
Or do I have to adapt the resource creation with:
[root at ha1 ~]# crm configure primitive pinggw ocf:pacemaker:ping \
> params host_list="192.168.101.1" multiplier="200" timeout="3" \
> op start timeout="60"

That gives no warnings (even if I would have expected the warning about the
monitor_0 timeout as I didn't set it...???)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100511/cad74b7a/attachment-0002.htm>