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
CRM_MON(8) [FIXME: manual] CRM_MON(8)
NAME
crm_mon - monitor the cluster's status
SYNOPSIS
crm_mon [-V] -d -pfilename -h filename
crm_mon [-V] [-1|-n|-r] -h filename
crm_mon [-V] [-n|-r] -X filename
crm_mon [-V] [-n|-r] -c|-1
crm_mon [-V] -i interval
crm_mon -?
DESCRIPTION
The crm_mon command allows you to monitor your cluster's status and configuration. Its output includes the number of nodes, uname, uuid,
status, the resources configured in your cluster, and the current status of each. The output of crm_mon can be displayed at the console or
printed into an HTML file. When provided with a cluster configuration file without the status section, crm_mon creates an overview of nodes
and resources as specified in the file.
OPTIONS
--help, -?
Provide help.
--verbose, -V
Increase the debug output.
--interval seconds, -i seconds
Determine the update frequency. If -i is not specified, the default of 15 seconds is assumed.
--group-by-node, -n
Group resources by node.
--inactive, -r
Display inactive resources.
--as-console, -c
Display the cluster status on the console.
--one-shot, -1
Display the cluster status once on the console then exit (does not use ncurses).
--as-html filename, -h filename
Write the cluster's status to the specified file.
--daemonize, -d
Run in the background as a daemon.
--pid-file filename, -p filename
Specify the daemon's pid file.
--xml-file filename, -X filename
Specify an XML file containing a cluster configuration and create an overview of the cluster's configuration.
EXAMPLES
Display your cluster's status and get an updated listing every 15 seconds:
crm_mon
Display your cluster's status and get an updated listing after an interval specified by -i. If -i is not given, the default refresh
interval of 15 seconds is assumed:
crm_mon -i interval[s]
Display your cluster's status on the console:
crm_mon -c
Display your cluster's status on the console just once then exit:
crm_mon -1
Display your cluster's status and group resources by node:
crm_mon -n
Display your cluster's status, group resources by node, and include inactive resources in the list:
crm_mon -n -r
Write your cluster's status to an HTML file:
crm_mon -h filename
Run crm_mon as a daemon in the background, specify the daemon's pid file for easier control of the daemon process, and create HTML output.
This option allows you to constantly create HTML output that can be easily processed by other monitoring applications:
crm_mon -d -p filename -h filename
Display the cluster configuration laid out in an existing cluster configuration file (filename), group the resources by node, and include
inactive resources. This command can be used for dry-runs of a cluster configuration before rolling it out to a live cluster.
crm_mon -r -n -X filename
FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.
AUTHOR
crm_mon was written by Andrew Beekhof.
[FIXME: source] 07/05/2010 CRM_MON(8)