similar to: heartbeat on xen 2.0.7

I'm configuring a HA-cluster to share disks using heartbeat from http://www.linux-ha.org/ Two machines, lets call them server1 and server2 share the same disk with an ocfs2 file system. However, the two machines have separate disks for their OS installations. The two physical servers have two gigabit nics each and on those nics I place four virtual IP addresses which heartbeat makes sure is

Hi, I have one physical server (server1 - CentOS 4) and one vmware (server2 - CentOS running in a VM under Windows 2003). I'm running PHP/MySQL webapps on it. I want to be sure there is a failover, but I don't really need load balancing for now. I run php/mysql/apache with the binaries that comes with CentOS 4. I have installed heartbeat on both and set MySQL replication so that

Hi, right now I am using only one external server as a gateway for the internal servers. I would like to enable a fail-over on a second server. To implement the floating VIP, should I use heartbeat+pacemaker? Or is there something more "lightweight"? Basically, I just need server2 up the VIP when server1 is down, and server2 down the VIP when server1 is back up (or server 1 does not up

# 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]:

This note describes a heartbeat technique for validating the integrity of a NUT installation. Introduction ------------ A NUT configuration may run for months with little or no output to a system administrator to assure that the combined processes are running correctly. The technique described in this note verifies that the ups driver, upsd, upsmon, upssched and upssched-cmd components are

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

I am stuck. This is X86_64 platform. In the extras repos, there is the SRPMS for heartbeat along with the RPMS for it. I have downloaded both. But I can't build the RPMS from the SRPM as it fails compiling something in BUILD/heartbeat-2.0.8/lib/crm/pengine Additionally, I can't install the RPMS: rpm -Uvh heartbeat-2.0.8-3.el5.centos.i386.rpm heartbeat-2.0.8-3.el5.centos.x86_64.rpm

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.

Hi all, I am new to Hearbeat so please be kind :) I also posted this on Linux-HA lists with no responses so I posted it here. I have successfully configure two machines to use heartbeat to cluster httpd. The two nodes are called etk-1 and etk-2. I am trying to configure another two machines to act as a separate cluster (on the same IP subnet). These two nodes are called radu-1 and radu-2.

Hello list, Working on migrating my existing High-Availability setups from CentOS 5.3 to 6.0, both x86_64. I generally setup a fairly simple 2 node active/passive cluster using DRBD , Heartbeat, and Pacemaker. Use these clusters to run our proprietary Medical software plus a few key services ( openvpn , Digi PortServer Daemon, etc.). I had a procedure in place for doing all of this under 5.3

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

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:

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

I checked, and I have it like this: # Name of the HA cluster created. # must be unique within the subnet HA_NAME="ganesha-nfs" # # The gluster server from which to mount the shared data volume. HA_VOL_SERVER="tlxdmz-nfs1" # # N.B. you may use short names or long names; you may not use IP addrs. # Once you select one, stay with it as it will be mildly unpleasant to # clean up

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:

Hi List, I've setup 2 openldap servers in n-way multimaster replication mode in a test environment, both run centos 6.2, this works well but now i'm trying to make these 2 servers failover using heartbeat. i've got no experience with heartbeat (or setting up clusters in general) however from what i understand heartbeat starts/stops the service if the server has the virtual IP

It is consistently happening 14-15 minutes after starting. Please see attached upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary upssched is used. Dan ________________________________ From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on behalf of Roger Price via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>

We have added heartbeat-2.0.4 for CentOS 4 into the testing repository at dev.centos.org. Copy the testing CentOS-Testing.repo file from here: http://dev.centos.org/centos/4/ to /etc/yum.repos.d/ , then use this command to install heartbeat: yum --enablerepo=c4-testing install heartbeat Report issues with this to the heartbeat-2.0 tracker here: http://bugs.centos.org/view.php?id=1305