similar to: CentOS 6: corosync and pacemaker won't stop (patch)

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

Hi, We''re setting up fairly large Lustre 2.1.2 filesystems, each with 18 nodes and 159 resources all in one Corosync/Pacemaker cluster as suggested by our vendor. We''re getting mixed messages on how large of a Corosync/Pacemaker cluster will work well between our vendor an others. 1. Are there Lustre Corosync/Pacemaker clusters out there of this size or larger? 2.

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

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

I'm trying to setup a pair of FreePBX-4.211.64 boxes using Pacemaker, Corosync, and DRBD. All the examples I've found so far use Heartbeat, but Heartbeat is not in the repositories and doesn't want to compile from source. Does anyone have a working configuration they can share or a tutorial they can point me to? Also, what does drbdlinks bring to the party? Isn't just linking

Greetings! I am working with Lustre-2.1.2 on RHEL 6.2. First I configured it using the standard defaults over TCP/IP. Everything worked very nicely usnig a real, static --mgsnode=a.b.c.x value which was the actual IP of the MGS/MDS system1 node. I am now trying to integrate it with Pacemaker-1.1.7. I believe I have most of the set-up completed with a particular exception. The "lctl

I'm currently testing fail-over with a two-node active-active cluster (with node dig and node dag): Both nodes are up, one is manually killed. CTDB on the node that's still alive should perform a recovery and everything should working again. What's infrequently happening is: After killing the pacemaker-process on dag (and dag consequently being fenced), dig's CTDB tries to

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

Dear All, Would like your advise if anyone have setup ocfs2 on oracle Linux 7 (free) with corosync and also pacemaker. I've search the net but all guide seem to be dated to 2012 and somehow outdated or I don't get it. I know that the ocfs2 default cluster lock o2cb don't support lock CTDB need thus need to change that to pacemaker and corosync. Please help. Regards, Min Wai.

Hi, I have two KVM hosts (CentOS 7) and would like them to operate as High Availability servers, automatically migrating guests when one of the hosts goes down. My question is: Is this even possible? All the documentation for HA that I've found appears to not do this. Am I missing something? My configuration so fare includes: * SAN Storage Volumes for raw device mappings for guest vms

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

Hi all, could somebody point me to what is considered a sound way to offer Xen guests on a two node DRBD cluster in combination with Pacemaker? I prefer block devices over images for the DomU''s. I understand that for live migration DRBD 8.3 is needed, but I''m not sure as to what kind of resource agents/technologies are advised (LVM,cLVM, ...) and what kind of DRBD config

On 22/06/16 01:01 AM, Tom Robinson wrote: > Hi, > > I have two KVM hosts (CentOS 7) and would like them to operate as High Availability servers, > automatically migrating guests when one of the hosts goes down. > > My question is: Is this even possible? All the documentation for HA that I've found appears to not > do this. Am I missing something? Very possible. It's

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

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:

I've been trying to build a model cluster using three virtual machines on my home server. Each VM boots off its own dedicated partition (CentOS 7.3). One partition is designated to be the common /home partition for the VMs, (on the real machine it will mount as /cluster). I'm intending to run GFS2 on the shared partition, so I need to configure DLM and corosync. That's where I'm

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:

Also you should probably use dovecot director to ensure same user sessions end up on same server, as it's not supported to access same user on different backends in this scenario. Aki > On 10/01/2020 19:49 Adrian Minta <adrian.minta at gmail.com> wrote: > > > > Hello, > > you need to "clone" the first server, change the ip address, mount the same

Hi hvjunk, could you please tell me have you had time to check my previous post? Could you please send me mentioned link to your Gluster Ansible scripts? Thank you, Adam On Sun, May 28, 2017 at 2:47 PM, Adam Ru <ad.ruckel at gmail.com> wrote: > Hi hvjunk (Hi Hendrik), > > "centos-release-gluster" installs "centos-gluster310". I assume it > picks the