similar to: Heartbeat for Centos 5- Can't build RPMS or install prebuilt RPMS

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

# activating extras repo # issuing "yum install heartbeat" # got : (...tons of depedencies resolution...) ttmkfdir-3.0.9-20.el4.i38 100% |=========================| 6.6 kB 00:00 ---> Package ttmkfdir.i386 0:3.0.9-20.el4 set to be updated --> Running transaction check Dependencies Resolved =============================================================================

I just recently upgraded a box from i386 5.3 -> 5.4. The box has heartbeat packages installed from "extras:" heartbeat-pils-2.1.3-3.el5.centos heartbeat-stonith-2.1.3-3.el5.centos heartbeat-devel-2.1.3-3.el5.centos heartbeat-2.1.3-3.el5.centos The heartbeat daemon no longer starts.. the init script reports a success, as well as the logs: May 4 22:33:10 fc-fmcln02 heartbeat: [9344]:

hello list! I am attempting to setup haproxy using a shared up I am trying to setup using the heartbeat package that I currently have installed: [root at VIRTCENT01:~]#rpm -qa | grep heartbeat | grep -v -e stonith -e pils heartbeat-2.1.4-11.el5 heartbeat-2.1.4-11.el5 I have /etc/ha/.d authkeys setup this way: # auth 2 #1 crc 2 sha1 {SHA}secret I have /etc/ha.d/resources setup like this:

Hi all. This is probably more of a HA list, or possibly even linux-practices, question but all hosts concerned are running CentOS and I reckon some of you guys might have some good suggestions. Feel free to tell me to piss off. :) I'm building a new CentOS, DRBD, Heartbeat and NFS HA cluster. We already have boxes running similar setups on FC2/3 running NFS v2/3 with the Ultra Monkey

I've just been trying to do a "yum update" on a Centos 4.6 system, and one of the packages it wants to upgrade is heartbeat-ldirectord from 2.1.2-3 to 2.1.3-2 However, the newer version has dependency problems that can't be resolved: [root at miton2 ~]# yum update Loading "fastestmirror" plugin Loading "protectbase" plugin Setting up Update Process Setting

CentOS Errata and Enhancement Advisory 2005:1130-2 CentOS 4 x86_86 drbd / heartbeat - Enhancement Update (Extras Only) We are pleased to add drbd (with integrated heartbeat) to the CentOS extras repository. DRBD is a block device which is designed to build high availability clusters. This is done by mirroring a whole block device via (a dedicated) network. You could see it as a network raid-1.

CentOS Errata and Enhancement Advisory 2005:1130-2 CentOS 4 i386 drbd / heartbeat - Enhancement Update (Extras Only) We are pleased to add drbd (with integrated heartbeat) to the CentOS extras repository. DRBD is a block device which is designed to build high availability clusters. This is done by mirroring a whole block device via (a dedicated) network. You could see it as a network raid-1.

I have a suggestion about the heartbeat and the way that "downed node" detection works. There are occasions where a node is up, and for whatever reason, I need to power cycle it (for instance, a frozen process, etc). In these instances, my other nodes are unable to perform file system operations until the heartbeat period expires. This ends up being somewhere around 30-60 seconds (this

Since I get so much from this list I thought I would share a project I've been working on and how it works with samba (3.0.1). It is Samba related so I hope it's not off topic. I've set up a HA solution with redundant Samba Domain Controllers throuth the "Heartbeat" package at: http://www.ultramonkey.org/download/heartbeat/1.1.3/redhat_9/ I have two "Redhat

CentOS 4.1 and Heartbeat 2.0.0. I'm trying to install the rpm's for heartbeat and heartbeat-stonith and get these failed dependencies. error: Failed dependencies: libcrypto.so.0.9.7 is needed by heartbeat-2.0.0-1.i586 libnet.so.0 is needed by heartbeat-2.0.0-1.i586 librpm-4.1.so is needed by heartbeat-2.0.0-1.i586 librpmdb-4.1.so is needed by

Greetings - Hoping to hear from hunner or one of the other maintainers of the puppetlabs corosync module - there is a note on the git project page that there is currently no way to configure STONITH. Is this information current? If so, has anybody come up with a simple method of managing STONITH with corosync via puppet? -- You received this message because you are subscribed to the

Hello List, Any suggestions to solve the following would be most appreciated. Setup: Active/Passive Two Node Cluster. Two UPSes (APC Smart-UPS 1500 C) with USB communication cables cross connected (ie UPS-webserver1 monitored by webserver2, and vice versa) to allow for stonith/fencing OS OpenSuse Leap 42.2 NUT version 2.7.1-2.41-x86_64 Fencing agent: external/nut Problem: When power fails to a

Roger, Thanks for your reply. As I understand it, for reliable fencing a node cannot be responsible for fencing itself, as it may not be functioning properly. Hence my "cross over" setup. The direct USB connection from Webserver1 to UPS-Webserver2 means that Webserver1 can fence (cut the power to) Webserver2 if the cluster software decides that it is necessary. If my UPSes were able to

On Fri, 22 Apr 2016, Digimer wrote: > Then you would use pacemaker to manage the floating IP, fence > (stonith) a lost node, and promote drbd->mount FS->start nfsd->start > floating IP. My favorite acronym: stonith -- shoot the other node in the head. -- Paul Heinlein heinlein at madboa.com 45?38' N, 122?6' W

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi all, I am following the guide on HowToForge to get Heartbeat going for two Apache web servers (http://www.howtoforge.com/high_availability_heartbeat_centos), a quick question for anyone who might have a similar setup. Do I have to assign the service IP to either of the NICs or does Heartbeat do that automagically? Thanks -- "The secret impresses no-one, the trick you use it for is

Hi list, I'm new to clustering, and I'm running a little cluster at home. The cluster is running on a workstation hardware and running on Centos 6.5. Component: corosync, pacemaker, drbd and pcs. All works good. This cluster has different resources: 1) drbd0 2) drbd1 3) drbd0_fs 4) drbd1_fs 5) pgsql 6) smb + nmb 7) libvirt (lbs) 8) libvirt_guests (lsb) I've this constraint

G92's seem to require some additional bit of initialization before the BSP engine can work. It feels like clocks are not set up for the underlying VLD engine, which means that all commands submitted to the xtensa chip end up hanging. VP seems to work fine though. This still allows people to force-enable the bsp engine if they want to play around with it, but makes it harder for the card to

Hi I have: SLES 10 SP2 (2.6.16.60-0.21-smp) ocfs2-tools-1.4.0-0.3 ocfs2console-1.4.0-0.3 and I can't change "heartbeat dead threshold" value. Content of /etc/sysconfig/o2cb: # O2CB_ENABLED: 'true' means to load the driver on boot. O2CB_ENABLED=true # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=ocfs2 # O2CB_HEARTBEAT_THRESHOLD: