`SAPHana` Slave reports `WAITING4PRIM` even when Primary seems to be running

Solution Unverified - Updated -

Issue

When SAPHana is started we can see that despite SAPHana being PROMOTED and PRIM on one node, the other node reports WAITING4PRIMARY and master for that node is -INFINITY

# pcs status --full
...
* Node node1 (1):
    + hana_sid_clone_state              : PROMOTED  
    + hana_sid_sync_state               : PRIM      
    + hana_sid_roles                    : 2:P:master1:master:worker:slave
...
* Node node2 (2):
    + hana_sid_clone_state              : WAITING4PRIM  
    + hana_sid_sync_state               : SFAIL      
    + hana_sid_roles                    : 2:S:master1:master:worker:slave
...

Environment

  • Red Hat Enterprise Linux 6, 7 with High Availability
  • running SAPHana cluster resource

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.