search for: heartbeat

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

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: Iterations before a node is conside...

...new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000034 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'heartbeat at localhost' UPSNAME we were launched to process 0.000041 [D1] parse_at: processing...

...new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000034 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'heartbeat at localhost' UPSNAME we were launched to process 0.000041 [D1] parse_at: processing...

...Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update) is the there is this line (Network UPS Tools upsmon 2.8.0) every five minutes. Jun 13 19:17:08 fricka upssched[1896873]: Timer daemon started Jun 13 19:17:08 fricka upssched[1896873]: New timer: heartbeat-failure-t...

...Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update) is the there is this line (Network UPS Tools upsmon 2.8.0) every five minutes. Jun 13 19:17:08 fricka upssched[1896873]: Timer daemon started Jun 13 19:17:08 fricka upssched[1896873]: New timer: heartbeat-failure-t...

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

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: VIRTC...

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. Obviously being a broadcast protocol radu-1 and radu-2 get these messages from etk-1 and I c...

...naged to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000053 [D1] parse_at: &...

...naged to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000053 [D1] parse_at: &...

...e investigation) confirming that the same daemon > handles operations from the new client instances, its strace now has > numerous FDs to report after select() - so I guess it is a problem of > detecting an exit of the counterpart. > > > > 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the > 'heartbeat at localhost' we were launched to process? > 0.000034 [D1] parse_at: 'heartbeat at localhost' in AT command > matched the 'heartbeat at localhost' UPSNAME we were launched to process > 0.000041 [D1] p...

...e investigation) confirming that the same daemon > handles operations from the new client instances, its strace now has > numerous FDs to report after select() - so I guess it is a problem of > detecting an exit of the counterpart. > > > > 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the > 'heartbeat at localhost' we were launched to process? > 0.000034 [D1] parse_at: 'heartbeat at localhost' in AT command > matched the 'heartbeat at localhost' UPSNAME we were launched to process > 0.000041 [D1] p...

...culprit, but I made the changes to my configuration. No change, after five minutes of starting nut, upssched will be running with 100% cpu usage. Any ideas what could be causing this? Here is my configuration and in the end are some log snippets: --------------------------------------------------- heartbeat.conf # heartbeat.conf -- 10 minute heartbeat ups.status: OL TIMER 300 ups.status: OB TIMER 300 --------------------------------------------------- hosts.conf MONITOR eaton5s at localhost "Eaton 5S 700" --------------------------------------------------- nut.conf MODE=netserver --------...

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

All, This is hopefully the final drop of the patches for adding global heartbeat to the o2cb stack. The diff from the previous set is here: http://oss.oracle.com/~smushran/global-hb-diff-2010-10-07 Implemented most of the suggestions provided by Joel and Wengang. The most important one was to activate the feature only at the end, Also, got mostly a clean run with checkpatch....

I have an OCFS2 filesystem on a coraid AOE device. It mounts fine, but with heavy I/O the server self fences claiming a write timeout: (16,2):o2hb_write_timeout:164 ERROR: Heartbeat write timeout to device etherd/e0.1p1 after 12000 milliseconds (16,2):o2hb_stop_all_regions:1789 ERROR: stopping heartbeat on all active regions. Kernel panic - not syncing: ocfs2 is very sorry to be fencing this system by panicing It is my understanding that OCFS is expecting that the only hea...

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

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 up repositories Loading mirror speeds...

Hi, We are using the heartbeat and drbd packages from latest centos (4.3) extras repository. Upon installation of both packages I noticed that if you "chkconfig heartbeat off" that will cause drbd to chkconfig'ed on. And visa versa. After doing some trouble shooting it turns out the "BEGIN INIT INFO" se...