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
heartbeat
HEARTBEAT(8) System administration utilitie HEARTBEAT(8)
NAME
heartbeat - Heartbeat subsystem for High-Availability Linux
DESCRIPTION
heartbeat is a basic heartbeat subsystem for Linux-HA. It will run scripts at initialisation, and when machines go up or down. This version
will also perform IP address takeover using gratuitous ARPs. It works correctly for a 2-node configuration, and is extensible to larger
configurations.
It implements the following kinds of heartbeats:
o UDP/IP broadcast;
o UDP/IP multicast;
o UDP/IP unicast;
o Bidirectional Serial Rings ("raw" serial ports) -- this type is deprecated and should no longer be used;
o special "ping" heartbeats for routers, etc. -- this type has been superseded by functionality in pacemaker() and should no longer be
used.
Comprehensive documentation on heartbeat is available in the Heartbeat User's Guide. If this documentation is not installed on your system,
it can be found at http://linux-ha.org/.
OPTIONS
The following options are supported by heartbeat:
-d
Increment debugging level. Higher levels are more verbose.
-r
Reload heartbeat. This option is functionally identical to sending a running heartbeat process a HUP signal. If the configuration has
not changed, then this option is essentially a no-op. If ha.cf(5) or authkeys(5) has changed, then heartbeat will re-read these files
and update its configuration.
This option may not be used together with -R.
-k
Kill (stop) heartbeat.
-s
Report heartbeat status.
-R
Heartbeat restart exec flag (internal use only). May not be used with -r.
-C
Heartbeat current resource state for restart (internal use only). Only valid with -R.
-V
Print out heartbeat version.
Note that most of these options are used for supporting the heartbeat init script, which provides the conventional start, stop, status and
restart options (among others). It is recommended to use this rather than invoking the heartbeat command directly.
SEE ALSO
ha.cf(5), authkeys(5)
AUTHORS
Alan Robertson <alanr@unix.sh>
heartbeat
Juan Pedro Paredes Caballero <juampe@retemail.es>
man page
Simon Horman <horms@verge.net.au>
man page
Florian Haas <florian.haas@linbit.com>
man page
Heartbeat 3.0.5 24 Nov 2009 HEARTBEAT(8)