similar to: OCFS2 + CMAN/PCMK Kernel Error

hi! i'm on debian lenny and trying to run ocfs2 on a dual primary drbd device. the drbd device is already set up as msDRBD0. to get dlm_controld.pcmk i installed it from source (from cluster-suite-3.0.10) now i configured a resource "resDLM" with 2 clones: primitive resDLM ocf:pacemaker:controld op monitor interval="120s" clone cloneDLM resDLM meta

Hello, this is my scenario: 1)I've created a Pacemaker cluster with the following ocfs package on opensuse 11.3 64bit ocfs2console-1.8.0-2.1.x86_64 ocfs2-tools-o2cb-1.8.0-2.1.x86_64 ocfs2-tools-1.8.0-2.1.x86_64 2)I've configured the cluster as usual : <resources> <clone id="dlm-clone"> <meta_attributes id="dlm-clone-meta_attributes">

I have been reading loads of threads over different mailing lists about ocfs2_controld, so have anyone ever built Cluster stack (openAIS, pacemaker, corosync + OCFS2 1.4) from source and got o2cb agent working with pacemaker? Got this from messages: /var/log/messages:Aug 14 15:05:20 ip-172-16-2-12 o2cb(resO2CB:0)[4239]: ERROR: Setup problem: couldn't find command:

I have seen many references online to being able to use OCFS2 with Pacemaker, but the documentation I have been able to find is very Sparse. I have kernel 2.6.29, and the latest DLM and Pacemaker (using openais) and OCFS2-Tools from GIT. (As of June 13). I was able to build ocfs2_controld.pcmk ... (With some minor changes to the makefile for my install) I noticed the OCF version of o2cb is not

If I start ocfs2_controld.cman in parallel on a few nodes, only one of them starts up, the others exit with one of these errors: call_section_read at 370: Reading from section "daemon_protocol" on checkpoint "ocfs2:controld" (try 1) call_section_read at 387: Checkpoint "ocfs2:controld" does not have a section named "daemon_protocol" call_section_read at

Fix compilation of Pacemaker glue for ocfs2_controld when the underlying Pacemaker installation supports both the Heartbeat and OpenAIS stack Signed-off-by: Andrew Beekhof <abeekhof at suse.de> --- upstream/ocfs2_controld/pacemaker.c 2008-09-11 16:51:11.000000000 +0200 +++ dev/ocfs2_controld/pacemaker.c 2008-10-23 13:14:56.000000000 +0200 @@ -20,8 +20,16 @@ #include

Hi Guys, I overhauled and simplified the Pacemaker hooks recently. This patch: - Reuses more code from the Pacemaker libraries - Escalates fencing to the cluster manager instead of initiating it directly Attached patch is against master, or you can pull the original patch which is against an older version used by SUSE:

Hello, We are having a problem with a 3-node cluster based on Pacemaker/Corosync with 2 primary DRBD+OCFS2 nodes and a quorum node. Nodes run on Debian Squeeze, all packages are from the stable branch except for Corosync (which is from backports for udpu functionality). Each node has a single network card. When the network is up, everything works without any problems, graceful shutdown of

Hello, I hope this mailing list is correct. I've a cluster pacemaker with a clone resource ocfs2 with ocfs2-tools-1.4.1-25.6.x86_64 ocfs2-tools-o2cb-1.4.1-25.6.x86_64 on Opensuse 11.2 After some network problem on my switch I receive on one of 4 nodes of my cluster the following messages Aug 18 13:12:28 nodo1 openais[8462]: [TOTEM] The token was lost in the OPERATIONAL state. Aug 18 13:12:28

Hello all, I am trying to create a corosync/pacemaker cluster using CentOS 6.0. However, I'm having a great deal of difficulty doing so. Corosync has a valid configuration file and an authkey has been generated. When I run /etc/init.d/corosync I see that only corosync is started. >From experience working with corosync/pacemaker before, I know that this is not enough to have a functioning

Hello, everybody.? ? ?I use?NFS to do live migration?After input ?virsh --connect=qemu:///system --quiet migrate --live vm12 qemu+tcp://pcmk-1/system ?(vm12 ?is vm name,/pcmk-1 is host name)it use almost 10s for preparation.?During the 10s,the vm is still runing and can ping other vm. But if i input mkdir pcmk-6 in vm during the 10s,it say :mkdir: cannot create directory `pcmk-6': Read-only

Using fsdlm/ocfs2_controld.cman, I've rerun the test I've been having problems with on 2.6.30-rc1. After running for several minutes in the same directory on three nodes, the test hangs, and I collect the following information: bull-01 ------- 3053 S< [ocfs2dc] ocfs2_downconvert_thread 3054 S< [dlm_astd] dlm_astd 3055 S< [dlm_scand]

Hi. Today I have updated my cluster installation with the version cman-2.0.115-1 through yum update. When I have started the cman service , it fails. If I execute cman_tool debug I get the following error : [CMAN ] CMAN 2.0.115 (built Sep 16 2009 12:28:10) started aisexec: symbol lookup error: /usr/libexec/lcrso/service_cman.lcrso: undefined symbol:

On 5/9/23 12:40 AM, Heming Zhao wrote: > Sorry for reply late, I am a little bit busy recently. > > On Fri, May 05, 2023 at 11:42:51AM +0800, Joseph Qi wrote: >> >> >> On 5/5/23 12:20 AM, Heming Zhao wrote: >>> On Thu, May 04, 2023 at 05:41:29PM +0800, Joseph Qi wrote: >>>> >>>> >>>> On 5/4/23 4:02 PM, Heming Zhao wrote:

CentOS Errata and Security Advisory 2007:0559 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2007-0559.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 75b4a925c1a8a7822d1f1b5d74afa20e cman-2.0.64-1.0.1.el5.i386.rpm b44560f1c706e76a466f0b293d95fe8c cman-devel-2.0.64-1.0.1.el5.i386.rpm Source:

CentOS Errata and Security Advisory 2007:0559 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2007-0559.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: a9a55193209abf2b0d1dcb4ff31e7ed6 cman-2.0.64-1.0.1.el5.x86_64.rpm b44560f1c706e76a466f0b293d95fe8c cman-devel-2.0.64-1.0.1.el5.i386.rpm

CentOS Errata and Bugfix Advisory 2008:0898 Upstream details at : https://rhn.redhat.com/errata/RHBA-2008-0898.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 03ea6dc53f1f8dafbdd7f1ed4ad89202 cman-2.0.84-2.el5_2.1.x86_64.rpm cde78e5a359c0dbc63ea1b30e17732cd cman-devel-2.0.84-2.el5_2.1.i386.rpm

CentOS Errata and Bugfix Advisory 2008:0898 Upstream details at : https://rhn.redhat.com/errata/RHBA-2008-0898.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: ffcd533b5e83a92e4336d44b7c617d41 cman-2.0.84-2.el5_2.1.i386.rpm f771de6845cefbe6d84fa9ef415e55cd cman-devel-2.0.84-2.el5_2.1.i386.rpm Source:

CentOS Errata and Bugfix Advisory 2008:1009 Upstream details at : https://rhn.redhat.com/errata/RHBA-2008-1009.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: d254c64fd5985ac3b382fafcd5a32182 cman-2.0.84-2.el5_2.2.i386.rpm 32cec9feb2953bcff8fbe2c7de28f02e cman-devel-2.0.84-2.el5_2.2.i386.rpm Source:

CentOS Errata and Bugfix Advisory 2008:1009 Upstream details at : https://rhn.redhat.com/errata/RHBA-2008-1009.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 12df1c2200932fd0acaf6e160c083f7c cman-2.0.84-2.el5_2.2.x86_64.rpm a4491c6082688ad759a8d97d1f37624b cman-devel-2.0.84-2.el5_2.2.i386.rpm