My Oracle Support Banner

Solaris Cluster 3.x Node/Server/System Panics With FailFast Ucmmd Died 30 Second Ago Message Resolution Path (Doc ID 1021789.1)

Last updated on AUGUST 11, 2020

Applies to:

Solaris Cluster - Version 3.0 to 3.3 U2 [Release 3.0 to 3.3]
Solaris Cluster Geographic Edition - Version 3.1x to 3.3 U2 [Release 3.1 to 3.3]
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)

Purpose

This document aids troubleshooting of Solaris Cluster node panics with the following message:

This panic string can be on system consle and/or in /var/adm/messages. It is also in vmcore. coredump. 
In almost all cases this occurs when ucmmd cluster daemon exits. Ucmmd like many other cluster daemons is being watched by failfast driver that triggers a system coredump when the daemon being registered does not return to the driver in a timeout value of 30 seconds. There are many reasons why ucmmd exits. This article will give you steps to find the underlying cause. This article does not cover much less frequently seen scenarios where ucmmd daemon is accidentally killed, victimized by a customer's script or dumps application core which likely to be a bug, or where system runs out of resources and it simply cannot run.

When you have a panic caused by ucmmd exit (died) you may see a single node panic, multiple nodes panic or all cluster nodes panic. You may see this on clusters configured with Oracle RAC and/or Oracle Cluster Ready Services (CRS) systems running oracle parallel database.

Troubleshooting Steps

To view full details, 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 a vibrant support community of peers and Oracle experts.