Dejan, You narrowed down the problem perfectly. My interface had ipv6 addresses but they were the auto-configured addresses with scope of link. I reconfigured it with a globally scoped address and starting the resource works fine now.
I really appreciate your input and thank you again! Dusty Mabe --- On Fri, 8/13/10, Dejan Muhamedagic <deja...@fastmail.fm> wrote: > From: Dejan Muhamedagic <deja...@fastmail.fm> > Subject: Re: [Pacemaker] IPv6addr resource error messages on startup > To: "The Pacemaker cluster resource manager" <pacemaker@oss.clusterlabs.org> > Date: Friday, August 13, 2010, 5:22 AM > Hi, > > On Thu, Aug 12, 2010 at 01:50:26PM -0700, Dusty Mabe > wrote: > > 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) > > Nope, these just parrot what you saw in the crm_mon output. > They > are obviously not coming from either lrmd or IPv6addr. > > > Nevertheless, I have copied all of the output here for > completeness: > [...] > > 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 > > Looking at the code, apparently this means that IPv6addr > cannot > find the interface which would match the parameters. Are > you sure > that your IPv6addr config is OK? Can you show us your > interfaces. > > Thanks, > > Dejan > > > > > > > > > > > --- On Thu, 8/12/10, Dejan Muhamedagic <deja...@fastmail.fm> > wrote: > > > > > From: Dejan Muhamedagic <deja...@fastmail.fm> > > > Subject: Re: [Pacemaker] IPv6addr resource error > messages on startup > > > To: "The Pacemaker cluster resource manager" > <pacemaker@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@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@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@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@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@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
