The is no "default" unless it's set, that's why crm complains
On Tue, May 11, 2010 at 12:41 PM, Gianluca Cecchi wrote:
> On Tue, May 11, 2010 at 5:47 PM, Vadym Chepkov wrote:
>
>> pingd is a daemon with is running all the time and does it job
>> you still need to define monitor operation thou
On Tue, May 11, 2010 at 5:47 PM, Vadym Chepkov wrote:
> pingd is a daemon with is running all the time and does it job
> you still need to define monitor operation though, what if the daemon dies?
> op monitor just have a different meaning for ping and pingd.
> with pingd - monitor daemon
> with
pingd is a daemon with is running all the time and does it job
you still need to define monitor operation though, what if the daemon dies?
op monitor just have a different meaning for ping and pingd.
with pingd - monitor daemon
with ping - monitor connectivity
as for warnings:
crm configure prop
On Tue, May 11, 2010 at 1:13 PM, Vadym Chepkov 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 pace
By the way, there is another issue with your config
Since you set multiplier to 100, it will negate your resource-stickiness which
is also set to 100.
Either reduce multiplier or increase default resource-stickiness ( I have mine
at 1000)
Vadym
On May 11, 2010, at 7:06 AM, Gianluca Cecchi wrot
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.
Here is my settings, they do work for me:
primitive ping ocf:pacemaker:ping \
On Tue, May 11, 2010 at 12:50 PM, Vadym Chepkov wrote:
> You forgot to turn on monitor operation for ping (actual job)
>
>
>
I saw from the
[r...@ha1 ~]# crm ra meta ping
command
Operations' defaults (advisory minimum):
start timeout=60
stop timeout=20
reload
You forgot to turn on monitor operation for ping (actual job)
On May 11, 2010, at 5:15 AM, Gianluca Cecchi wrote:
> On Mon, May 10, 2010 at 4:39 PM, Vadym Chepkov wrote:
> # crm ra meta ping
>
> name (string, [undef]): Attribute name
> The name of the attributes to set. This is the name t
On Tue, May 11, 2010 at 11:58 AM, Dejan Muhamedagic
wrote:
> Do you see the attribute set in the status section (cibadmin -Ql
> | grep -w pingd)? If not, then the problem is with the resource.
[r...@ha1 ~]# cibadmin -Ql | grep -w pingd
Tried to ch
Hi,
On Tue, May 11, 2010 at 11:15:49AM +0200, Gianluca Cecchi wrote:
> On Mon, May 10, 2010 at 4:39 PM, Vadym Chepkov wrote:
>
> > # crm ra meta ping
> >
> > name (string, [undef]): Attribute name
> > The name of the attributes to set. This is the name to be used in the
> > constraints.
> >
On Mon, May 10, 2010 at 4:39 PM, Vadym Chepkov wrote:
> # crm ra meta ping
>
> name (string, [undef]): Attribute name
> The name of the attributes to set. This is the name to be used in the
> constraints.
>
> By default is "pingd", but you are checking against pinggw
>
> I suggest you do not
# crm ra meta ping
name (string, [undef]): Attribute name
The name of the attributes to set. This is the name to be used in the
constraints.
By default is "pingd", but you are checking against pinggw
I suggest you do not change name though, but adjust your location constraint
to use pingd i
Hello,
using pacemaker 1.0.8 on rh el 5 I have some problems understanding the way
ping clone works to setup monitoring of gw... even after reading docs...
As soon as I run:
crm configure location nfs-group-with-pinggw nfs-group rule -inf:
not_defined pinggw or pinggw lte 0
the resources go stopp
13 matches
Mail list logo
