12-24-2019
You lost all heartbeats from node 1 to node 2 - thats the reason for the crash. This might happen when your system is simply too busy - but since you should have both heartbeat on disk and heartbeat via network, you should think that there is time enough to send at least one every couple of seconds, Your cluster heartbeat settings might be too tight - giving it more time for the heartbeat might help preventing this issue in the future.
Just out of curiosity - using GPFS and HACMP and RAC on the same systems appears to me to be a completely unnecessary setup, as you are running essentially 3 different cluster products on a system when RAC alone would suffice. Why ?
This User Gave Thanks to zxmaus For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. HP-UX
hi friends,
i know that when there is a crash then that memory image is
put into /var/adm/crash
but if the system hangs up and if i have access to console of
that machine then how can i take the crash dump manully.
thanks (2 Replies)
Discussion started by: mxms755
2 Replies
3. Solaris
Can anyone of you help me in enabling crash dump on Solaris 5.5.1 (1 Reply)
Discussion started by: csreenivas
1 Replies
4. AIX
Hi Guys,
I have two nodes clustered. Each node is AIX 5.2 & they are clustered with HACMP 5.2. The mode of the cluster is Active/Passive which mean one node is the Active node & have all resource groups on it & the 2nd node is standby.
Last Monday I noted that all resource groupes have been... (2 Replies)
Discussion started by: aldowsary
2 Replies
5. Solaris
hi ,
i have machine that is crashed
how i can enable core dump file & how can i find it ? :confused: (4 Replies)
Discussion started by: lid-j-one
4 Replies
6. UNIX for Advanced & Expert Users
Hi.
I have started heartbeat on two redhat servers. Using eth0.
Before I start heartbeat I can ping the two server to each other.
Once I start heartbeat both the server become active as they both have warnings that the other node is dead.
Also I am not able to ping each other. After stopping... (1 Reply)
Discussion started by: amrita garg
1 Replies
7. AIX
Hi Guys,
I have to design a multinode hacmp cluster and am not sure if the design I am thinking of makes any sense.
I have to make an environment that currently resides on 5 nodes more resilient but I have the constrain of only having 4 frames. In addition the business doesnt want to pay for... (7 Replies)
Discussion started by: zxmaus
7 Replies
8. AIX
Hi
I had an active passive cluster. Node A went down and all resource groups moved to Node B.
Now we brought up Node A. What is the procedure to bring everything back to Node A.
Node A #lssrc -a | grep cl
clcomdES clcomdES 323782 active
clstrmgrES cluster... (9 Replies)
Discussion started by: samsungsamsung
9 Replies
9. HP-UX
Hi Experts,
I have configured HP-UX Service Guard cluster and it dumps crash every time i reboot a cluster node. Can anyone please help me to prevent these unnecessary crash dumps at the time of rebooting SG cluster node?
Thanks in advance.
Vaishey (2 Replies)
Discussion started by: Vaishey
2 Replies
10. OS X (Apple)
MacPro (2013) 12-Core, 64GB RAM (today's crash):
panic(cpu 2 caller 0xffffff7f8b333ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (318824 seconds ago): 31883, last successful... (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT DEBIAN
apphbd
APPHBD(8) System administration utilitie APPHBD(8)
NAME
apphbd - Application Heartbeat Monitor for High-Availability Linux
SYNOPSIS
apphbd [-srkdh] [-c file]
DESCRIPTION
Warning
apphbd is deprecated; its use is strongly discouraged. The functionality provided by apphbd has been replaced by resource-level
monitoring in Pacemaker.
/usr/lib/heartbeat/apphbd is a basic application heartbeat monitor daemon for Linux-HA. A group of Application Heartbeat APIs are defined
for this heartbeat monitoring service. Applications may register with the daemon in order to be monitored. If an application fails to send
a heartbeat within the specified interval, the daemon will log an event.
apphbd may use a watchdog timer to monitor itself.
apphbd extends its functionality by using plugins. A plugin, recmgr notifies the recovery manager daemon if certain events occur (e.g. an
application fails to heartbeat).
The Recovery Manager daemon (/usr/lib/heartbeat/recoverymgrd) receives notification from the recmgr plugin, then it tries to execute
recovery scripts as configured. See the recoverymgrd default configuration file, recoverymgrd.conf for details.
recoverymgrd registers itself with apphbd as a client application. apphbd should be started first with the recmgr plugin loaded. Then,
recoverymgrd should be configured and started
OPTIONS
The following options are supported:
-s
Show the status of apphbd, running or stopped.
-k
Stop (kill) the daemon.
-r
Restart the daemon. apphbd will reload its configuration file when restarted.
-d level
Set the debug level.
-h
Show a brief usage message.
-c file
Set an alternate configuration file. The default configuration file is ./apphbd.cf. For details on the file format and supported
options, refer to the example apphbd.cf file found in the documentation directory.
FILES
o /var/run/apphbd.pid - default PID file
o apphbd.cf - Default configuration file for apphbd. apphbd searches the file in its working directory.
o recoverymgrd.conf - default configuration file for recoverymgrd. recoverymgrd searches the file in its working directory. An
alternative configuration file may be specified on the command line.
o /usr/lib/heartbeat/plugins/AppHBNotification - directory containing plugins for apphbd.
SEE ALSO
heartbeat(8)
AUTHORS
Alan Robertson <alanr@unix.sh>
apphbd
Andrea Brugger <andrea.l.brugger@intel.com>
man page
Florian Haas <florian.haas@linbit.com>
man page
Heartbeat 3.0.5 November 26, 2009 APPHBD(8)