[Pacemaker] IPv6addr resource error messages on startup

Dusty Mabe dustymabe at yahoo.com
Thu Aug 12 20:50:26 UTC 2010 

Hi,

I captured the output from var log messages while grepping for IPv6addr. The output was captured during an execution of crm resource start myIPv6addr. The significant messages seem to be:


Aug 12 16:01:18 hasync-1b crmd: [5754]: info: te_rsc_command: Initiating action 18: start myIPv6addr_start_0 on hasync-1a
Aug 12 16:01:19 hasync-1b crmd: [5754]: WARN: status_from_rc: Action 18 (myIPv6addr_start_0) on hasync-1a failed (target: 0 vs. rc: 1): Error

and 

Aug 12 16:01:19 hasync-1b pengine: [5952]: WARN: unpack_rsc_op: Processing failed op myIPv6addr_start_0 on hasync-1a: unknown error (1)



Nevertheless, I have copied all of the output here for completeness:


Aug 12 16:01:18 hasync-1b cib: [5750]: info: log_data_element: cib:diff: -       <primitive id="myIPv6addr" >
Aug 12 16:01:18 hasync-1b cib: [5750]: info: log_data_element: cib:diff: -         <meta_attributes id="myIPv6addr-meta_attributes" >
Aug 12 16:01:18 hasync-1b cib: [5750]: info: log_data_element: cib:diff: -           <nvpair value="Stopped" id="myIPv6addr-meta_attributes-target-role" />
Aug 12 16:01:18 hasync-1b cib: [5750]: info: log_data_element: cib:diff: +       <primitive id="myIPv6addr" >
Aug 12 16:01:18 hasync-1b cib: [5750]: info: log_data_element: cib:diff: +         <meta_attributes id="myIPv6addr-meta_attributes" >
Aug 12 16:01:18 hasync-1b cib: [5750]: info: log_data_element: cib:diff: +           <nvpair value="Started" id="myIPv6addr-meta_attributes-target-role" />
Aug 12 16:01:18 hasync-1b pengine: [5952]: notice: native_print: myIPv6addr     (ocf::heartbeat:IPv6addr):      Stopped
Aug 12 16:01:18 hasync-1b pengine: [5952]: notice: RecurringOp:  Start recurring monitor (30s) for myIPv6addr on hasync-1a
Aug 12 16:01:18 hasync-1b pengine: [5952]: notice: LogActions: Start myIPv6addr (hasync-1a)
Aug 12 16:01:18 hasync-1b crmd: [5754]: info: te_rsc_command: Initiating action 18: start myIPv6addr_start_0 on hasync-1a
Aug 12 16:01:19 hasync-1b crmd: [5754]: WARN: status_from_rc: Action 18 (myIPv6addr_start_0) on hasync-1a failed (target: 0 vs. rc: 1): Error
Aug 12 16:01:19 hasync-1b crmd: [5754]: WARN: update_failcount: Updating failcount for myIPv6addr on hasync-1a after failed start: rc=1 (update=INFINITY, time=1281643279)
Aug 12 16:01:19 hasync-1b crmd: [5754]: info: abort_transition_graph: match_graph_event:272 - Triggered transition abort (complete=0, tag=lrm_rsc_op, id=myIPv6addr_start_0, magic=0:1;18:405:0:1ba2020b-6cc6-48b2-8a76-5d872cd37017, cib=0.117.2) : Event failed
Aug 12 16:01:19 hasync-1b crmd: [5754]: info: match_graph_event: Action myIPv6addr_start_0 (18) confirmed on hasync-1a (rc=4)
Aug 12 16:01:19 hasync-1b pengine: [5952]: WARN: unpack_rsc_op: Processing failed op myIPv6addr_start_0 on hasync-1a: unknown error (1)
Aug 12 16:01:19 hasync-1b pengine: [5952]: notice: native_print: myIPv6addr     (ocf::heartbeat:IPv6addr):      Started hasync-1a FAILED
Aug 12 16:01:19 hasync-1b pengine: [5952]: notice: RecurringOp:  Start recurring monitor (30s) for myIPv6addr on hasync-1a
Aug 12 16:01:19 hasync-1b pengine: [5952]: notice: LogActions: Recover resource myIPv6addr      (Started hasync-1a)
Aug 12 16:01:19 hasync-1b crmd: [5754]: info: te_rsc_command: Initiating action 2: stop myIPv6addr_stop_0 on hasync-1a
Aug 12 16:01:21 hasync-1b crmd: [5754]: info: match_graph_event: Action myIPv6addr_stop_0 (2) confirmed on hasync-1a (rc=0)
Aug 12 16:01:21 hasync-1b pengine: [5952]: WARN: unpack_rsc_op: Processing failed op myIPv6addr_start_0 on hasync-1a: unknown error (1)
Aug 12 16:01:21 hasync-1b pengine: [5952]: notice: native_print: myIPv6addr     (ocf::heartbeat:IPv6addr):      Stopped
Aug 12 16:01:21 hasync-1b pengine: [5952]: info: get_failcount: myIPv6addr has failed 1000000 times on hasync-1a
Aug 12 16:01:21 hasync-1b pengine: [5952]: WARN: common_apply_stickiness: Forcing myIPv6addr away from hasync-1a after 1000000 failures (max=1000000)
Aug 12 16:01:21 hasync-1b pengine: [5952]: notice: RecurringOp:  Start recurring monitor (30s) for myIPv6addr on hasync-1b
Aug 12 16:01:21 hasync-1b pengine: [5952]: notice: LogActions: Start myIPv6addr (hasync-1b)
Aug 12 16:01:21 hasync-1b crmd: [5754]: info: te_rsc_command: Initiating action 18: start myIPv6addr_start_0 on hasync-1b (local)
Aug 12 16:01:21 hasync-1b crmd: [5754]: info: do_lrm_rsc_op: Performing key=18:407:0:1ba2020b-6cc6-48b2-8a76-5d872cd37017 op=myIPv6addr_start_0 )
Aug 12 16:01:21 hasync-1b lrmd: [5751]: info: rsc:myIPv6addr:297: start
Aug 12 16:01:21 hasync-1b IPv6addr: [22318]: ERROR: no valid mecahnisms
Aug 12 16:01:21 hasync-1b crmd: [5754]: info: process_lrm_event: LRM operation myIPv6addr_start_0 (call=297, rc=1, cib-update=1104, confirmed=true) unknown error
Aug 12 16:01:21 hasync-1b crmd: [5754]: WARN: status_from_rc: Action 18 (myIPv6addr_start_0) on hasyn




--- On Thu, 8/12/10, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:

> From: Dejan Muhamedagic <dejanmm at fastmail.fm>
> Subject: Re: [Pacemaker] IPv6addr resource error messages on startup
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Date: Thursday, August 12, 2010, 3:33 PM
> Hi,
> 
> On Thu, Aug 12, 2010 at 11:17:50AM -0700, Dusty Mabe
> wrote:
> > Hi,
> > 
> > I am having a problem trying to get
> ocf::heartbeat:IPv6addr to work with pacemaker. I keep
> getting the following message 
> > 
> > WARN: unpack_rsc_op: Processing failed op
> myIPv6addr_start_0 on hasync-1a: unknown error (1)
> 
> It could be anything. Did you check for error messages in
> the
> logs? Look for those coming from IPv6addr and lrmd.
> 
> Thanks,
> 
> Dejan
> 
> > My configuration for the resource is as follows:
> > 
> > primitive myIPv6addr ocf:heartbeat:IPv6addr \
> >     params ipv6addr="1234:5678::9999"
> cidr_netmask="64" nic="bond0.3" \
> >     op monitor interval="30s"
> > 
> > I have configured an IPaddr2 resource successfully but
> am not having luck with the IPv6addr resource. Have you guys
> seen this before?
> > 
> > I am on pacemaker 1.0.8, heartbeat 3.0.3,
> resource-agents 1.0.3, and cluster-glue 1.0.5.
> > 
> > 
> > 
> > Thanks for any help!
> > 
> > Dusty
> > 
> > 
> > 
> >       
> > 
> > _______________________________________________
> > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
> 
> _______________________________________________
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>

More information about the Pacemaker mailing list