Solaris Cluster 3.2 Node/System/Server may Report 'Resource temporarily unavailable' if rpc.fed Breaches project.max-contracts (Doc ID 1928781.1)

Last updated on AUGUST 01, 2016

Applies to:

Solaris Cluster - Version 3.2 12/06 to 3.2U3 12/09 [Release 3.2]
Solaris Operating System - Version 10 3/05 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

 Solaris Cluster 3.2 nodes may report 'Unable to Fork ... Resource temporarily unavilable' in /var/adm/messages and console, eg:

 There are many reasons for these messages discussed in other documents including, but not limited to:

 This document covers a specific issue known to exist in Solaris Cluster 3.2 when the number of in-use contracts breaches the value defined by projects.max-contracts (10,000 by default)

Changes

 No known changes are required to encounter this situation.  Long uptime and active workloads may eventually encounter the condition discussed in this document.

Cause

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