Why does a SAPInstance resource unexpectedly failover when using the `sap_cluster_connector`?

Solution Verified - Updated -

Issue

  • Unexpected failover of the SAPInstance cluster resources when the monitor operation detects the status GRAY:
SAPInstance(SID_SCS<InstanceNumber>)[pid]: ERROR: SAP instance service msg_server is not running with status GRAY !
SAPInstance(SID_SCS<InstanceNumber>)[pid]: ERROR: SAP instance service enserver is not running with status GRAY !
SAPInstance(SID_SCS<InstanceNumber>)[pid]: ERROR: SAP instance service gwrd is not running with status GRAY !
  • The number of file descriptors limit for the user SIDadm is reached.
  • The file sapstartsrv.log reports the following message around the time the SAPInstance resource reports the SAP instance has status GRAY:
SAP HA Trace: === SAP_HA_CheckConfig ===
SAP HA Error: num_active_calls overflowSAP HA Trace: Fire system command /usr/bin/sap_cluster_connector hcc ...

Environment

Red Hat Enterprise Linux 8 with High-Availability Add-on
Pacemaker cluster running SAPInstance resources
sap_cluster_connector is configured for the SAPInstance

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content