The problem I was having was identified in the other thread: 1.0.9 vs. 1.0.9.1. However, I still don't have a clear picture if pacemaker can be configured to use corosync and not to use openais and how. My speculation is the "compatibility: none" option in corosync.conf but keep the "--with-ais" in pacemaker's configure command line options. Do you know the answer? Alan
On Wed, Aug 4, 2010 at 1:18 AM, Andrew Beekhof <and...@beekhof.net> wrote: > On Tue, Aug 3, 2010 at 2:23 AM, Alan Jones <falanclus...@gmail.com> wrote: > > I'd like to configure pacemaker to use corosync without the openais > package. > > We have our own custom Linux distro, so I'm trying to compile: > > > > Pacemaker-1-0-Pacemaker-1.0.9.tar.bz2 > > Reusable-Cluster-Components-8286b46c91e3.tar.bz2 > > corosync-1.2.7.tar.gz > > > > The relevent options seem to be: > > > > - configure options for pacemaker: --without-heartbeat-support --with-ais > > > > checking corosync/coroipcc.h usability... yes > > checking corosync/coroipcc.h presence... yes > > checking for corosync/coroipcc.h... yes > > checking for OpenAIS branch... corosync > > checking for coroipcc_msg_send_reply_receive in -lcoroipcc... yes > > checking for supported stacks... corosync > > Features = ncurses corosync snmp > > Stack Libraries = -lcoroipcc > > > > - corosync.conf: > > > > compatibility: none > > > > corosync [MAIN ] Compatibility mode set to none. Using V2 of the > > synchronization engine. > > > > However, cib won't start. When I start it by hand I get: > > Yeah, don't do that. > The "normal" startup process sets a number of environment variables > which tell the pacemaker daemons how to behave. > > What logging do you get when corosync tries to start it? > You'll need to include much more of the corosync output for us to be > able to help. > > > > > -bash-3.00# /usr/lib64/heartbeat/cib > > cib[27290]: 2010/08/02_16:56:45 info: G_main_add_TriggerHandler: Added > > signal manual handler > > cib[27290]: 2010/08/02_16:56:45 info: G_main_add_SignalHandler: Added > signal > > handler for signal 17 > > cib[27290]: 2010/08/02_16:56:45 info: retrieveCib: Reading cluster > > configuration from: /ddr/var/lib/heartbeat/crm/cib.xml (digest: > > /ddr/var/lib/heartbeat/crm/cib.xml.sig) > > cib[27290]: 2010/08/02_16:56:45 info: startCib: CIB Initialization > completed > > successfully > > cib[27290]: 2010/08/02_16:56:45 info: crm_cluster_connect: Unsupported > > cluster stack: (null) > > cib[27290]: 2010/08/02_16:56:45 CRIT: cib_init: Cannot sign in to the > > cluster... terminating > > > > Please advise. > > > > > > _______________________________________________ > > 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
