similar to: Is Pacemaker integration ready to go?

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">

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:

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

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

Hello, Is there *any* way to reliablily determine the NetBIOS name of a computer when you only know their IP address? I know it is very easy to find the IP address from the NetBIOS name, but I can't seem to find any way of getting a NetBIOS name from an IP.. James deBoer (jdeboer@scsinternet.com)

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

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:

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

Hello Everyone, Coming accross this once in a while. It's the test environemnt so not very important, and it does take a lot of abuse. Maybe it's of interest to someone. Starting cluster: Checking if cluster has been disabled at boot... [ OK ] Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I think I stumbled on at least two bugs in the CentOS 7.2 pacemaker package, though I'm not quite sure if or where to report it. I'm using the following package to set up a 2-node active/passive cluster: [root at clnode1 ~]# rpm -q pacemaker pacemaker-1.1.13-10.el7_2.4.x86_64 The installation is up-to-date on both nodes as of the

Hi, Can u please explain for what purpose pacemaker cluster used here? Regards, Jiffin On Thursday 07 December 2017 06:59 PM, Tomalak Geret'kal wrote: > > Hi guys > > I'm wondering if anyone here is using the GlusterFS OCF resource > agents with Pacemaker on CentOS 7? > > yum install centos-release-gluster > yum install glusterfs-server

Hi I have a trouble with my shorewall. I have 5 Ips adresses on my internet interface. I can ping any of these adresses, but the traffic take always the base adresse on my interface. All the traffic is on the same adress, but I what to know the traffric for each of these adresses. I search a lot to find the setting for do that, I don''t know what is wrog in my config, somebody can

Hi guys I'm wondering if anyone here is using the GlusterFS OCF resource agents with Pacemaker on CentOS 7? yum install centos-release-gluster yum install glusterfs-server glusterfs-resource-agents The reason I ask is that there seem to be a few problems with them on 3.10, but these problems are so severe that I'm struggling to believe I'm not just doing something wrong. I created

Hi everyone, I need some help to setup my configuration failover system. My goal is to have a redundance system using Xen + DRBD + Corosync + Pacemaker On Xen I will have one virtual machine. When this computer has network down, I will do a Live migration to the second computer. The first configuration I will need is a crossover cable, won''t I? It is really necessary? Ok, I did it. eth0

Hello Fellow CentOS users. I was hoping to get some information on Pacemaker clusters using OCFS2 on CentOS 6.x. In my initial attempts to get this to work, I realized that Pacemaker is packaged much differently on CentOS than it is on Debian or SUSE. For example, /usr/sbin/dlm_controld.pcmk is missing and ocfs2-tools is nowhere to be found. Users could of course pull in packages from say Oracle

Hello, When I install the package Rsafd, I get the following message. > install.packages("Rsafd",repos="http://R-Forge.R-project.org ",dependecies=TRUE) Warning in install.packages("Rsafd", repos = "http://R-Forge.R-project.org", : argument 'lib' is missing: using '/Users/aajd/Library/R/2.10/library' Warning: unable to access index for

Some more information... No traffic must be on 64.254.229.230 , all must be on 64.254.229.226,64.254.229.227 and 64.254.229.229, but almost all the traffic is on 64.254.229.230. this is the trouble Incoming 64.254.229.226 : 125K Incoming 64.254.229.227 : 257K Incoming 64.254.229.228 :

Hi everyone, To be short, I try to compile the Distro kernel release 2.6.32-279.2.1.el6.centos.plus.x86_64, but I always got an error telling "missing-syscalls". I try and try and search, this morning on the CentOS Forum to find nothing on this subject. What is the solution, my CentOS Gurus? Have a great day Martin

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

> > With the node in standby (just one is online in this example, but another > is configured), I then set up the resources: > > pcs node standby > pcs resource create gluster_data ocf:heartbeat:Filesystem > device="/dev/cl/lv_drbd" directory="/gluster" fstype="xfs" > pcs resource create glusterd ocf:glusterfs:glusterd > pcs resource create