similar to: Asterisk HA with heartbeat and systemd

Hi, I'm using heartbeat as a failover for my asterisk server. on the active server 1 i have 10.10.10.1 eth0 10.10.10.3 secondary eth0 asterisk listens to the secondary ip, so that if server 1 fails, server 2 will then get that IP. so if server 1 fails, server 2 will have the IP 10.10.10.2 eth0 10.10.10.3 secondary eth0 problem is i have to bind asterisk to the secondary IP if dont, i

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.

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

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

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

Hello, I'm beginning to give up on making Linux-HA's heartbeat work for my environment (CentOS x86_64) and am wondering what other option have I got to help me: 1. Use IPVS to maintain a cluster of virtual servers, either master/slave or load-balanced. 2. Use DRBD in master/slave fashion to keep a home-grown application highly-available. The first thing I stumbled upon is RedHat Cluster

Hi all, I have two servers ZEUS (MASTER - 192.168.2.11) and POSEIDON (SLAVE - 192.168.2.12) with HeartBeat+DRBD+SAMBA installed ; HeartBeat is controlling SAMBA. I have a big partition which are mirrored /share. I moved all important directory on it. For example: # mv /var/lib/samba /share/cluster/varlibsamba # mv /var/cache/samba /share/cluster/varcachesamba and I make a link for each one: # ln

Hi, How should I handle the combinatorics when one config file must be built for a combination of possible classes? Take for example the amd automounter''s configuration file, which on Debian is found at /etc/am-utils/amd.conf. This is an INI style file which looks like: [fsname1] param1=foo param2=bar [fsname2] param1=baz param2=quag In my case I have one class of machines

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 have searched your FAQ''s and read the documentation on your site as well as googling. I am not able to figure this out. If you have any ideas can you please help. I am using the linux-ha failover with redundant firewalls. As part of the function of the linux-ha software consists a service called heartbeat which is a connection from each failover node through a serial cable or ethernet.

Has anyone worked with getting dovecot to work in a HA cluster using heartbeat? If so do you have any magic startup scripting or other special sauce? [I'll be playing with this over the next couple of days, although concentrating on pop for our requirements. I can post any scripting I produce] Nigel. -- [ Nigel Metheringham Nigel.Metheringham at InTechnology.co.uk ] [ -

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

Hello, Has anyone got Heartbeat 1.2.5 (latest Heartbeat 1 version) to compile and run on CentOS 5? I downloaded the source but hit difficulties compiling it, presumebly because it was never quite tweaked to run on the latest version. Thanks, --Amos

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

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:

Hello OCFS2 team, I'm currently looking at the OCFS2 code in linux-2.6.17.11, and i wander why OCFS2 performs its heartbeat on a disk region unlike on the network like many clustered services stack do. What is the requirement for a disk heartbeat ? Is there any way to tune this behaviour and change it into a network heartbeat ? -- Mathieu

On Thu, 28 Mar 2024, Dan Grostick via Nut-upsuser wrote: > All three systems have a heartbeat-timer failure approximately 15 minutes > after starting NUT. No subsequent failures. Any ideas on what is happening? I've seen the timers: heartbeat.conf has two 300 sec timers, upssched.cmd looks like what is often called upssched.conf and has a 660 sec timer. So it looks as if the

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:

On Fri, 29 Mar 2024, Dan Grostick wrote: > 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. After the heartbeat failure, is upsd still running? Does the command "upsc -L" report the UPS's? If you use systemd, what does the command

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