similar to: broken pipe question

Hi Dale, I am in fact doing all the items you suggest. here is a log. For normal commands I am logging off just fine. Its just the heartbeat command I am getting an error on when logging out. Thoughts? Jerry ------ asterisk_command() Action: Login asterisk_command() Username: XXXXX asterisk_command() Secret: XXXXX asterisk_command() Events: off asterisk_execute() event_list=0 ret=36

Dear all, I want to make call through socket i have set code given below: #!/usr/bin/perl -w use IO::Socket::INET; sub asterisk_command () { # my $command=$_[0]; my $ami=IO::Socket::INET->new(PeerAddr=>'127.0.0.1',PeerPort=>5038,Proto=>'tcp') or die "failed to connect to AMI!"; print $ami "Action: Login\r\nUsername:

I am getting a priveldged command error on the manager API. 16-Feb-09 11:51 am asterisk_command() Action: Login 16-Feb-09 11:51 am asterisk_command() Username: XXX 16-Feb-09 11:51 am asterisk_command() Secret: ZZZZ 16-Feb-09 11:51 am asterisk_command() Events: off 16-Feb-09 11:51 am DEBUG: Response: Success[CR ][LF ]Message: Authentication accepted[CR ][LF ][CR ][LF ] 16-Feb-09 11:51 am

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

After launching the command several times, with debug (posted by 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

After launching the command several times, with debug (posted by 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

Hi, 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)

Hi, 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)

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, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

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:

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

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.

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

So, got some good news: I hear(*) I managed 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

So, got some good news: I hear(*) I managed 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

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

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

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" sections appear to be the cause. drbd has: ### BEGIN INIT INFO #

I'm a greenhorn when it comes to clustering in RHEL/CentOS and recently setup an active/standby clustering using Apache & Heartbeat. It seems to be a good entry step into clustering however after testing it I was disappointed in that the resource manager does not start httpd on node2 if httpd on node1 is dead (only starts httpd on node2 if the heartbeat daemon on node1 is dead). Is there