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 OCTOBER 09, 2019
Applies to:Solaris Cluster - Version 3.2 to 3.2 U3 [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)
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:
- How to resolve "fork: Resource temporarily unavailable" or "svc.startd: Could not create thread" issues (Doc ID 1266839.1)
- -Bash: Fork: Resource Temporarily Unavailable (Doc ID 1279664.1)
- Memory exhaustion leading to system hang on Solaris 10u11 (or kernel 147147-26) with ZFS (Doc ID 1573006.1)
- Process Creation on Solaris 10 and Solaris 11 Systems With Certain Kernel Patches Installed May Fail When Using a ZFS Volume as a Swap Device (Doc ID 1579923.1)
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)
No known changes are required to encounter this situation. Long uptime and active workloads may eventually encounter the condition discussed in this document.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!