<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: [Pacemaker] Could not connect to the CIB service: connection failed</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi,<BR>
<BR>
I don't know if it is just my versions or my configuration but use_mgmtd and/or use_logd cause pacemaker to<BR>
fail to start with the following configurations and RPMs (I'm running RHEL 5.5 with clusterlabs repo)<BR>
Let me know if you spot something amiss<BR>
<BR>
Thanks,<BR>
<BR>
Brett<BR>
<BR>
<BR>
RPMS:<BR>
corosync-1.2.7-1.1.el5<BR>
corosync-libs-1.2.7-1.1.el5<BR>
cluster-glue-1.0.6-1.6.el5<BR>
cluster-glue-libs-1.0.6-1.6.el5<BR>
heartbeat-3.0.3-2.el5.x86_64.rpm<BR>
heartbeat-libs-3.0.3-2.el5.x86_64.rpm<BR>
openais-1.1.3-1.6.el5.x86_64.rpm<BR>
openaislib-1.1.3-1.6.el5.x86_64.rpm<BR>
pacemaker-1.0.9.1-1.15.el5<BR>
pacemaker-libs-1.0.9.1-1.15.el5<BR>
resource-agents-1.0.3-2.6.el5<BR>
<BR>
Configuration:<BR>
/etc/corosync/corosync.conf:<BR>
compatibility: none<BR>
aisexec {<BR>
user: root<BR>
group: root<BR>
}<BR>
<BR>
totem {<BR>
version: 2<BR>
<BR>
# How long before declaring a token lost (ms)<BR>
token: 5000<BR>
<BR>
# How many token retransmits before forming a new configuration<BR>
token_retransmits_before_loss_const: 20<BR>
<BR>
# How long to wait for join messages in the membership protocol (ms)<BR>
join: 1000<BR>
<BR>
# How long to wait for consensus to be achieved before starting a new round of membership configuration (ms)<BR>
consensus: 7500<BR>
<BR>
# Turn off the virtual synchrony filter<BR>
vsftype: none<BR>
<BR>
# Number of messages that may be sent by one processor on receipt of the token<BR>
max_messages: 20<BR>
<BR>
# Disable encryption<BR>
secauth: off<BR>
<BR>
# How many threads to use for encryption/decryption<BR>
threads: 0<BR>
<BR>
# Limit generated nodeids to 31-bits (positive signed integers)<BR>
clear_node_high_bit: yes<BR>
<BR>
# Optionally assign a fixed node id (integer)<BR>
# nodeid: 1234<BR>
<BR>
interface {<BR>
ringnumber: 0<BR>
bindnetaddr: 10.16.2.0<BR>
mcastaddr: 239.255.5.2<BR>
mcastport: 694<BR>
}<BR>
}<BR>
<BR>
logging {<BR>
fileline: off<BR>
to_stderr: no<BR>
to_logfile: yes<BR>
to_syslog: no<BR>
logfile: /var/log/corosync.log<BR>
debug: off<BR>
timestamp: on<BR>
logger_subsys {<BR>
subsys: AMF<BR>
debug: off<BR>
}<BR>
}<BR>
<BR>
amf {<BR>
mode: disabled<BR>
}<BR>
<BR>
--END--<BR>
<BR>
/etc/corosync/service.d/pcmk:<BR>
service {<BR>
# Load the Pacemaker Cluster Resource Manager<BR>
name: pacemaker<BR>
ver: 0<BR>
# Either of these causes pacemaker to fail to start<BR>
#use_mgmtd: yes<BR>
#use_logd: yes<BR>
}<BR>
<BR>
--END--<BR>
<BR>
-----Original Message-----<BR>
From: Dejan Muhamedagic [<A HREF="mailto:dejanmm@fastmail.fm">mailto:dejanmm@fastmail.fm</A>]<BR>
Sent: Tue 17/08/2010 13:01<BR>
To: The Pacemaker cluster resource manager<BR>
Subject: Re: [Pacemaker] Could not connect to the CIB service: connection failed<BR>
<BR>
Hi,<BR>
<BR>
On Tue, Aug 17, 2010 at 10:28:01AM +0100, Brett Delle Grazie wrote:<BR>
> Hi,<BR>
><BR>
> Are you using backports or the madkis repository?<BR>
> For lenny you should be using backports.<BR>
><BR>
> I had a similar problem, remove the 'use_logd' and 'use_mgmtd' lines from your<BR>
> service entry for pacemaker. Try just removing the use_logd first.<BR>
><BR>
> I think the current version(s) of pacemaker no longer use logd or the service<BR>
> definition in corosync no longer supports it.<BR>
<BR>
Really? Hmm, nobody told me. At any rate, that'd be a serious<BR>
regression and would break some existing installations.<BR>
Otherwise, it could be that it's unintentionally broken. If so,<BR>
then the packages need to be fixed.<BR>
<BR>
> btw, my service definition for pacemaker is in a separate file in /etc/corosync/services.d/<BR>
><BR>
> (or some similar directory - I can't quite remember and I'm not at my system at the moment).<BR>
<BR>
/etc/corosync/service.d<BR>
<BR>
Thanks,<BR>
<BR>
Dejan<BR>
<BR>
><BR>
> Hope this helps.<BR>
><BR>
> Brett<BR>
><BR>
><BR>
> -----Original Message-----<BR>
> From: Bastian Schern [<A HREF="mailto:ml04@reventix.de">mailto:ml04@reventix.de</A>]<BR>
> Sent: Tue 17/08/2010 10:08<BR>
> To: The Pacemaker cluster resource manager<BR>
> Subject: [Pacemaker] Could not connect to the CIB service: connection failed<BR>
> <BR>
> Hallo,<BR>
><BR>
> I tried to install Pacemaker with Corosync on Debian Lenny based on the<BR>
> HowTo: <A HREF="http://www.clusterlabs.org/wiki/Debian_Lenny_HowTo">http://www.clusterlabs.org/wiki/Debian_Lenny_HowTo</A><BR>
><BR>
> Some month ago I already set up my first working Cluster on Lenny<BR>
> without any problems.<BR>
><BR>
> But now on two new hosts I'm not able to get the CRM working. Corosync<BR>
> itself seems to work.<BR>
><BR>
> I attached my corosync.conf and the corresponding log lines.<BR>
><BR>
> Does anybody know what's going wrong?<BR>
><BR>
> Thanks<BR>
> Bastian<BR>
><BR>
</FONT>
</P>
<BR>
______________________________________________________________________<BR>
This email has been scanned by the MessageLabs Email Security System.<BR>
For more information please visit http://www.messagelabs.com/email <BR>
______________________________________________________________________<BR>
</BODY>
</HTML>