[Pacemaker] help

Alex Samad - Yieldbroker Alex.Samad at yieldbroker.com
Thu May 22 02:10:35 UTC 2014


Strange for me :) the unknowledgeable

Did more testing and it works without the start and stop


thanks
Alex 



> -----Original Message-----
> From: Andrew Beekhof [mailto:andrew at beekhof.net]
> Sent: Thursday, 22 May 2014 11:59 AM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] help
> 
> Not strange, you can't specify an interval for non-recurring operations like
> start/stop
> 
> On 21 May 2014, at 9:15 pm, Alex Samad - Yieldbroker
> <Alex.Samad at yieldbroker.com> wrote:
> 
> > Hi
> >
> > I have removed the start and stop ops from the 2 resources and it seems to
> be okay now ...
> >
> > Very strange..
> > A
> >
> >> -----Original Message-----
> >> From: Alex Samad - Yieldbroker
> >> Sent: Wednesday, 21 May 2014 9:04 PM
> >> To: 'pacemaker at oss.clusterlabs.org'
> >> Subject: help
> >>
> >> Hi
> >>
> >> Seems like I thought I had a working system but I don't.
> >>
> >> 2 node setup
> >>
> >> Cluster Name: ybrp
> >> Corosync Nodes:
> >>
> >> Pacemaker Nodes:
> >> uatrp1 uatrp2
> >>
> >> Resources:
> >> Resource: ybrpip (class=ocf provider=heartbeat type=IPaddr2)
> >>  Attributes: ip=10.32.40.50 cidr_netmask=24 nic=eth0
> >> clusterip_hash=sourceip-sourceport
> >>  Meta Attrs: stickiness=0,migration-threshold=3,failure-timeout=600s
> >>  Operations: start on-fail=restart interval=0s timeout=60s
> >> (ybrpip-start-
> >> interval-0s)
> >>              monitor on-fail=restart interval=5s timeout=20s
> >> (ybrpip-monitor-
> >> interval-5s)
> >>              stop interval=0s timeout=60s (ybrpip-stop-interval-0s)
> >> Clone: ybrpstat-clone
> >>  Meta Attrs: globally-unique=false clone-max=2 clone-node-max=1
> >>  Resource: ybrpstat (class=ocf provider=yb type=proxy)
> >>   Meta Attrs: stickiness=100
> >>   Operations: start on-fail=restart interval=10s timeout=60s
> >> (ybrpstat-start-
> >> interval-10s)
> >>               monitor on-fail=restart interval=5s timeout=20s
> >> (ybrpstat-monitor-
> >> interval-5s)
> >>               stop interval=10s timeout=60s
> >> (ybrpstat-stop-interval-10s)
> >>
> >> Stonith Devices:
> >> Fencing Levels:
> >>
> >> Location Constraints:
> >> Ordering Constraints:
> >>  start ybrpstat-clone then start ybrpip (Mandatory)
> >> (id:order-ybrpstat-clone-
> >> ybrpip-mandatory)
> >> Colocation Constraints:
> >>  ybrpip with ybrpstat-clone (INFINITY)
> >> (id:colocation-ybrpip-ybrpstat-clone-
> >> INFINITY)
> >>
> >> Cluster Properties:
> >> cluster-infrastructure: cman
> >> dc-version: 1.1.10-14.el6_5.2-368c726
> >> last-lrm-refresh: 1400667913
> >> no-quorum-policy: ignore
> >> stonith-enabled: false
> >>
> >> I created my own resource ybrpstat from one of the other scripts
> >>
> >> But I am getting these
> >>
> >> May 21 20:41:11 uatrp1 pengine[2413]:   notice: unpack_config: On loss of
> >> CCM Quorum: Ignore
> >> May 21 20:41:11 uatrp1 pengine[2413]:    error: RecurringOp: Invalid
> >> recurring action ybrpstat-start-interval-10s wth name: 'start'
> >> May 21 20:41:11 uatrp1 pengine[2413]:    error: RecurringOp: Invalid
> >> recurring action ybrpstat-stop-interval-10s wth name: 'stop'
> >> May 21 20:41:11 uatrp1 pengine[2413]:    error: RecurringOp: Invalid
> >> recurring action ybrpstat-start-interval-10s wth name: 'start'
> >> May 21 20:41:11 uatrp1 pengine[2413]:    error: RecurringOp: Invalid
> >> recurring action ybrpstat-stop-interval-10s wth name: 'stop'
> >>
> >>
> >>
> >> I have done a set -x and captured the output from the script and I
> >> return 0
> >>
> >>
> >> I tried this
> >>
> >> crm_verify -L -V
> >>   error: RecurringOp:  Invalid recurring action
> >> ybrpstat-start-interval-10s wth
> >> name: 'start'
> >>   error: RecurringOp:  Invalid recurring action
> >> ybrpstat-stop-interval-10s wth
> >> name: 'stop'
> >>   error: RecurringOp:  Invalid recurring action
> >> ybrpstat-start-interval-10s wth
> >> name: 'start'
> >>   error: RecurringOp:  Invalid recurring action
> >> ybrpstat-stop-interval-10s wth
> >> name: 'stop'
> >> Errors found during check: config not valid
> >>
> >> Now I am lost ...
> >>
> >> A
> >
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >
> > Project Home: http://www.clusterlabs.org Getting started:
> > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org





More information about the Pacemaker mailing list