On Thu, Feb 4, 2010 at 10:06 PM, E-Blokos <in...@e-blokos.com> wrote: > > ----- Original Message ----- From: "Andrew Beekhof" <and...@beekhof.net> > To: <pacema...@clusterlabs.org> > Sent: Thursday, February 04, 2010 3:48 PM > Subject: Re: [Pacemaker] fedora 10 package update from yum > > > On Thu, Feb 4, 2010 at 7:38 PM, E-Blokos <in...@e-blokos.com> wrote: >> >> ----- Original Message ----- From: "Andrew Beekhof" <and...@beekhof.net> >> To: <pacema...@clusterlabs.org> >> Cc: <pacema...@clusterlabs.org> >> Sent: Thursday, February 04, 2010 2:21 AM >> Subject: Re: [Pacemaker] fedora 10 package update from yum >> >> >> On Wed, Feb 3, 2010 at 4:58 PM, E-Blokos <in...@e-blokos.com> wrote: >>> >>> ----- Original Message ----- From: "Oscar Remírez de Ganuza Satrústegui" >>> <oscar...@unav.es> >>> To: <pacema...@clusterlabs.org> >>> Sent: Wednesday, February 03, 2010 10:56 AM >>> Subject: Re: [Pacemaker] fedora 10 package update from yum >>> >>> >>>> _______________________________________________ >>>> Pacemaker mailing list >>>> Pacemaker@oss.clusterlabs.org >>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>>> >>> >>> I use >>> >>> openais-0.80.5-15.1.x86_64 >>> pacemaker-1.0.5-4.2.x86_64 >>> libopenais-devel-0.80.5-15.1.x86_64 >> >> why do you need this last one installed? >> >>> >>> installed from old opensuse repo >> >> Its probably just easiest to remove the old set of packages before >> installing the new ones. >> I don't think the OBS ones followed the fedora naming conventions - >> that might be causing problems. >> >> >> >> Hi Andrew, >> >> I removed libopenais from all the cluster and >> I tried to update on node from 5 in total. >> now when I restart the updated node : >> >> service openais start >> Starting OpenAIS (corosync): /usr/libexec/lcrso/quorum.lcrso: open failed: >> /usr/libexec/lcrso/quorum.lcrso: undefined symbol: >> sync_primary_callback_fn >> corosync [MAIN ] Corosync Cluster Engine ('1.2.0'): started and ready to >> provide service. >> corosync [MAIN ] Corosync built-in features: nss rdma >> corosync [MAIN ] Corosync Executive couldn't open configuration component >> 'openaisserviceenable' >> corosync [MAIN ] Corosync Cluster Engine exiting with status -9 at >> main.c:1304. >> >> is it because I should shut down and update all the node ? > > Don't think so, Steve (from the corosync project) might have more of an > idea. > I think I recall seeing it discussed before, perhaps try searching the > openais mailing list. > > _______________________________________________ > > > > I didn't know now it needs to run corsync to make openais works... > until now it didn't need it... mmhmm, maybe it's better I stay with the > working version... > too much other work now :(
A few seconds googling turned up: Try replacing the existing exported symbol in your /etc/init.d/openais file with: export COROSYNC_DEFAULT_CONFIG_IFACE="openaisserviceenableexperimental:corosync_parser" Which was endorsed by Steve as the correct solution. _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker