Solaris Cluster 3.x/4.x Node/System/Server is Currently Hangs or Hung Resolution Path (Doc ID 1020614.1)

Last updated on AUGUST 15, 2016

Applies to:

Solaris Cluster - Version 3.1 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)

Goal

Applications controlled by Sun Solaris Cluster hang, OS and/or Sun Solaris Cluster commands fail to complete or node generally becomes unresponsive
or unreachable

Overview: 


        This document is designed to help diagnose the cases where customer states one or more nodes in a cluster
	are currently hung by further refining what may be hung. 

	NOTE: This document is not designed for cases when the node was 'hung' and then rebooted, nor for cases where a postmortem
	with a core is requested.

 

Background:


	By definition, a system hang is when the entire system is unresponsive and the only remedy is to send the system a break signal and generate a core dump.

	Part of the difficulty in working with system hangs is knowing whether or not the system is actually hung. Sometimes it appears that the system is
	hung when in fact only a particular application is hung. For example users of a database may report that "the system is hung" when in fact the system
	itself is still running but the database application has hung.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms