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

Last updated on MARCH 13, 2024

Applies to:

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