----- Original Message -----
From: "Daniel Qian" <dan...@bestningning.com>
To: <pacemaker@oss.clusterlabs.org>
Sent: Thursday, December 31, 2009 12:32 PM
Subject: Re: [Pacemaker] ocfs2_controld: Unable to connect to CKPT:
Objectdoes not exist
----- Original Message -----
From: "Daniel Qian" <dan...@bestningning.com>
To: "Jiaju Zhang" <jjzhang.li...@gmail.com>;
<pacemaker@oss.clusterlabs.org>
Sent: Thursday, December 31, 2009 11:20 AM
Subject: Re: [Pacemaker] ocfs2_controld: Unable to connect to CKPT:
Objectdoes not exist
----- Original Message -----
From: "Jiaju Zhang" <jjzhang.li...@gmail.com>
To: "Daniel Qian" <dan...@bestningning.com>
Sent: Thursday, December 31, 2009 3:27 AM
Subject: Re: [Pacemaker] ocfs2_controld: Unable to connect to CKPT:
Object does not exist
On Thu, Dec 31, 2009 at 3:57 PM, Daniel Qian <dan...@bestningning.com>
wrote:
----- Original Message ----- From: "Jiaju Zhang"
<jjzhang.li...@gmail.com>
To: <pacemaker@oss.clusterlabs.org>; "Daniel Qian"
<dan...@bestningning.com>
Sent: Thursday, December 31, 2009 2:26 AM
Subject: Re: [Pacemaker] ocfs2_controld: Unable to connect to CKPT:
Object
does not exist
On Thu, Dec 31, 2009 at 11:35 AM, Daniel Qian <dan...@bestningning.com>
wrote:
I am using pacemaker, corosync and ocfs2 on Fedora 12 to build an
active/active cluster. When I try to start up o2cb resource with
ocfs2-tools-pcmk-1.4.3-3.fc12.x86_64 that comes with Fedora 12 it
produces
the following errors:
Dec 30 22:06:29 ilo150 corosync[3866]: [pcmk ] info: pcmk_notify:
Enabling node notifications for child 9178 (0x1e5e5f0)
Dec 30 22:06:29 ilo150 ocfs2_controld[9178]: Unable to connect to
CKPT:
Object does not exist
Does anyone know if this is a problem on the ocfs2 side or corosync
side?
- Have you installed openais package?
- ocfs2_controld is using the CKPT service which is provided by openais
- not corosync.
really? I did not know that. So my best bet is either switch to openais
or
You might misunderstand what I said. It is not "switch to openais" but
"install
the openais as well". That is to say, both corosync and openais package
are needed :)
I am getting a little confused now and maybe I missed some information
here. On the other cluster where openais is in use I had to set the
cluster communication - authkey, totem and interface etc. With this one I
am working on I did pretty much the same in corosync. Now you are saying
I need to turn on openais to work with corosync but the question is where
I should put those settings? openais.conf, corosync.conf or both? and
which package is supposed to start up pacemaker processes which are done
through corosync at the moment:
1111 ? Ssl 0:10 corosync
1117 ? SLs 0:00 \_ /usr/lib64/heartbeat/stonithd
1118 ? S 0:03 \_ /usr/lib64/heartbeat/cib
1119 ? S 0:01 \_ /usr/lib64/heartbeat/lrmd
1120 ? S 0:00 \_ /usr/lib64/heartbeat/attrd
1121 ? S 0:00 \_ /usr/lib64/heartbeat/pengine
1122 ? S 0:02 \_ /usr/lib64/heartbeat/crmd
I got more confused now. On Fedora 12 if I do 'service openais status' I
get a response saying corosync is running. Looking into the startup script
/etc/rc.d/init.d/openais everything is pointing to corosync actually:
prog="corosync"
exec="/usr/sbin/corosync"
lockfile="/var/lock/subsys/corosync"
Something I learned in a hard way - although corosync can do most of the
stuff previous versions of openais does it wont work with ocfs2 by itself in
my case. I stopped corosync and started openais. The openais on Fedora 12
started corosync in turn and the problem is magically gone. from the init
script of openais all it does is to start corosync. I still dont know where
that extra touch is that fixed the issue. Hopefully my posting here will at
least help out those wading through the same maze.
Happy new yar
Daniel
_______________________________________________
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
