[Pacemaker] Could not connect to the CIB service: connection failed

[Brett Delle Grazie]

Hi,

I don't know if it is just my versions or my configuration but use_mgmtd and/or use_logd cause pacemaker to
fail to start with the following configurations and RPMs (I'm running RHEL 5.5 with clusterlabs repo)
Let me know if you spot something amiss

Thanks,

Brett


RPMS:
corosync-1.2.7-1.1.el5
corosync-libs-1.2.7-1.1.el5
cluster-glue-1.0.6-1.6.el5
cluster-glue-libs-1.0.6-1.6.el5
heartbeat-3.0.3-2.el5.x86_64.rpm
heartbeat-libs-3.0.3-2.el5.x86_64.rpm
openais-1.1.3-1.6.el5.x86_64.rpm
openaislib-1.1.3-1.6.el5.x86_64.rpm
pacemaker-1.0.9.1-1.15.el5
pacemaker-libs-1.0.9.1-1.15.el5
resource-agents-1.0.3-2.6.el5

Configuration:
/etc/corosync/corosync.conf:
compatibility: none
aisexec {
        user: root
        group: root
}

totem {
        version: 2

        # How long before declaring a token lost (ms)
        token:          5000
 
        # How many token retransmits before forming a new configuration
        token_retransmits_before_loss_const: 20
 
        # How long to wait for join messages in the membership protocol (ms)
        join:           1000
 
        # How long to wait for consensus to be achieved before starting a new round of membership configuration (ms)
        consensus:      7500

        # Turn off the virtual synchrony filter
        vsftype:        none
 
        # Number of messages that may be sent by one processor on receipt of the token
        max_messages:   20
 
        # Disable encryption
        secauth:        off
 
        # How many threads to use for encryption/decryption
        threads:        0
        
        # Limit generated nodeids to 31-bits (positive signed integers)
        clear_node_high_bit: yes
        
        # Optionally assign a fixed node id (integer)
        # nodeid:         1234

        interface {
                ringnumber: 0
                bindnetaddr: 10.16.2.0
                mcastaddr: 239.255.5.2
                mcastport: 694
        }
}

logging {
        fileline: off
        to_stderr: no
        to_logfile: yes
        to_syslog: no
        logfile: /var/log/corosync.log
        debug: off
        timestamp: on
        logger_subsys {
                subsys: AMF
                debug: off
        }
}

amf {
        mode: disabled
}

--END--

/etc/corosync/service.d/pcmk:
service {
        # Load the Pacemaker Cluster Resource Manager
        name: pacemaker
        ver:  0
        # Either of these causes pacemaker to fail to start
        #use_mgmtd: yes
        #use_logd: yes 
}

--END--

-----Original Message-----
From: Dejan Muhamedagic [mailto:dejanmm at fastmail.fm]
Sent: Tue 17/08/2010 13:01
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Could not connect to the CIB service: connection failed
 
Hi,

On Tue, Aug 17, 2010 at 10:28:01AM +0100, Brett Delle Grazie wrote:
> Hi,
> 
> Are you using backports or the madkis repository?
> For lenny you should be using backports.
> 
> I had a similar problem, remove the 'use_logd' and 'use_mgmtd' lines from your 
> service entry for pacemaker.  Try just removing the use_logd first.
> 
> I think the current version(s) of pacemaker no longer use logd or the service 
> definition in corosync no longer supports it.

Really? Hmm, nobody told me. At any rate, that'd be a serious
regression and would break some existing installations.
Otherwise, it could be that it's unintentionally broken. If so,
then the packages need to be fixed.

> btw, my service definition for pacemaker is in a separate file in /etc/corosync/services.d/
>
> (or some similar directory - I can't quite remember and I'm not at my system at the moment).

/etc/corosync/service.d

Thanks,

Dejan

> 
> Hope this helps.
> 
> Brett
> 
> 
> -----Original Message-----
> From: Bastian Schern [mailto:ml04 at reventix.de]
> Sent: Tue 17/08/2010 10:08
> To: The Pacemaker cluster resource manager
> Subject: [Pacemaker] Could not connect to the CIB service: connection failed
>  
> Hallo,
> 
> I tried to install Pacemaker with Corosync on Debian Lenny based on the 
> HowTo: http://www.clusterlabs.org/wiki/Debian_Lenny_HowTo
> 
> Some month ago I already set up my first working Cluster on Lenny 
> without any problems.
> 
> But now on two new hosts I'm not able to get the CRM working. Corosync 
> itself seems to work.
> 
> I attached my corosync.conf and the corresponding log lines.
> 
> Does anybody know what's going wrong?
> 
> Thanks
> 	Bastian
> 

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100818/90cb76fc/attachment-0001.html>