Sponsored Content
Operating Systems AIX Crash dump and Panic message : RSCT Dead Man Switch Timeout for HACMP; halting non-responsive node Post 303042277 by Neo on Friday 20th of December 2019 05:36:14 AM
Old 12-20-2019
Well, it appears to me you have a performance issue (resource issue) causing the failure.

It could be a disk error, a bus error, or a file system error causing the I/O problem; or like the message says, it could be a memory issue.

So, you should probably look in your syslog files and boot messages for errors related to the above recommendations:

Code:
  
        Recommended Actions
        Examine I/O and memory activity on the system
        Reduce load on the system
        Tune virtual memory parameters

I would start at the top (look for errors in log files) first.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

help, what is the difference between core dump and panic dump?

help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies

2. HP-UX

crash dump

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

crash dump

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

Node Switch Reasons in HACMP

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

crash dump

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

Linux heartbeat on redhat 4:node dead

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

hacmp in a 7 node configuration ?

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

HACMP switch over

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

Prevent crash dump when SG cluster node reboots

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)

MacOS 10.15.2 Catalina display crash and system panic

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
scds_syslog_debug(3HA)					 Sun Cluster HA and Data Services				    scds_syslog_debug(3HA)

NAME
scds_syslog_debug - write a debugging message to the system log SYNOPSIS
cc [flags...] -I /usr/cluster/include file -L /usr/cluster/lib -l dsdev #include <rgm/libdsdev.h> void scds_syslog_debug(int debug_level, constchar *format... DESCRIPTION
The scds_syslog_debug() function writes a debugging message to the system log. It uses the facility returned by the scha_cluster_getlogfa- cility(3HA) function. All syslog messages are prefixed with: SC[<resourceTypeName>,<resourceGroupName>,<resourceName>,<methodName> If you specify a debug_level greater than the current debugging level being used, no information is written. The DSDL defines the maximum debugging level, SCDS_MAX_DEBUG_LEVEL, as 9. The scds_initialize(3HA) function, which the calling program must call before scds_syslog_debug(), retrieves the current debugging level from the file: /var/cluster/rgm/rt/<resourceTypeName>/loglevel. Caution - Messages written to the system log are not internationalized. Do not use gettext() or other message translation functions in conjunction with this function. PARAMETERS
The following parameters are supported: debug_level Debugging level at which this message is to be written. Valid debugging levels are between 1 and SCDS_MAX_DEBUG_LEVEL, which is defined as 9 by the DSDL. If the specified debugging level is greater than the debugging level set by the calling program, the message is not written to the system log. format Message format string, as specified by printf(3C) ... Variables, indicated by the format parameter, as specified by printf(3C) EXAMPLES
Example 1 Display All Debugging Messages To see all debugging messages for resource type SUNW.iws, issue the following command on all nodes of your cluster echo 9 > /var/cluster/rgm/rt/SUNW.iws/loglevel Example 2 Suppress Debugging Messages To suppress debugging messages for resource type SUNW.iws, issue the following command on all nodes of your cluster echo 0 > /var/cluster/rgm/rt/SUNW.iws/loglevel FILES
/usr/cluster/include/rgm/libdsdev.h Include file /usr/cluster/lib/libdsdev.so Library ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscdev | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
printf(3C), scds_syslog(3HA), scha_cluster_getlogfacility(3HA), syslog(3C), syslog.conf(4), attributes(5) Sun Cluster 3.2 7 Sep 2007 scds_syslog_debug(3HA)
All times are GMT -4. The time now is 06:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy