Hello,
I got the same problem, i think i used the latest version of resource agents.
# ra info IPaddr2
Operations' defaults (advisory minimum):
start timeout=90
stop timeout=100
status interval=10s timeout=20s start-delay=0
monitor_10 interval=10s timeout=20s start-delay=0
Then I changed the depth value on IPaddr2 from 10 to 0.
<action name="monitor" depth="10" timeout="20s" interval="10s"
start-delay="0" />
to:
<action name="monitor" depth="0" timeout="20s" interval="10s"
start-delay="0" />
Then reconfigure ip resource. The problem has gone.
Is it possible to do that?
and how about the status line? Do I have to change to depth="0" too?
<action name="status" depth="10" timeout="20s" interval="10s"
start-delay="0" />
I was installing from source:
RA: Cluster-Resource-Agents-5f09e3bd7e20
Pacemaker 1.0.6 : Pacemaker-1-0-cd2aaf7e35cf
Regards,
QUoc
On Tue, Dec 8, 2009 at 5:41 PM, Marian Marinov <[email protected]> wrote:
> If anyone encounter such problems, please check your version of resource-
> agents.
>
> With my setup, the problem was older resource-agents package which for some
> reason was not upgraded by yum.
>
> Regards,
> Marian
>
> On Monday 07 December 2009 12:33:13 Marian Marinov wrote:
>> I have filed a bug report about this issue:
>>
>> http://developerbugs.linux-foundation.org/show_bug.cgi?id=2242
>>
>> On Monday 07 December 2009 06:18:13 Marian Marinov wrote:
>> > Hello,
>> > I'm just setting up a new HA solution and decided to go with the latest
>> > peacemaker. However I have encountered some very strange problems:
>> >
>> > crm(live)# cib use t1
>> > crm(t1)# configure
>> > crm(t1)configure# property stonith-enabled=false
>> > crm(t1)configure# show
>> > node $id="0f519a50-98e0-4bc2-8fb9-6bc28d87461c" fiona
>> > node $id="57db28bf-a58e-4b98-a9a9-03e65bce2431" shrek
>> > property $id="cib-bootstrap-options" \
>> > dc-version="1.0.6-f709c638237cdff7556cb6ab615f32826c0f8c06" \
>> > cluster-infrastructure="Heartbeat" \
>> > stonith-enabled="false"
>> > crm(t1)configure# primitive failover-ip ocf:heartbeat:IPaddr params
>> > ip=10.3.0.1 op monitor interval=10s
>> > ERROR: failover-ip: action monitor_0 does not exist
>> > crm(t1)configure# primitive failover-ip ocf:heartbeat:IPaddr2 params
>> > ip=10.3.0.1 cidr_netmask=32 op monitor interval=10s
>> > ERROR: failover-ip: action monitor_0 does not exist
>> > crm(t1)configure# primitive failover-ip ocf:heartbeat:IPaddr2 params
>> > ip=10.3.0.1 cidr_netmask=32 interval=10s
>> > ERROR: failover-ip: parameter interval does not exist
>> > crm(t1)configure# primitive failover-ip ocf:heartbeat:IPaddr2 params
>> > ip=10.3.0.1 cidr_netmask=32
>> >
>> >
>> > What I can't understand is where did the monitor operation disappear?
>> >
>> > I'm currently using similar setup on one year old setup without any
>> > issues. What am I missing.
>> >
>> > The setup is:
>> > CentOS 5.4
>> > Heartbeat: Version : 3.0.1 Release : 1.el5
>> > Pacemaker: Version : 1.0.6 Release : 1.el5
>> >
>> > I'm not using openais.
>>
>
> --
> Best regards,
> Marian Marinov
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
