Pacemaker staying in Waiting for startup-trigger from SBD

This document (000020942) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise High Availability 15 SP4

Situation

When trying to configure a new cluster with SBD_PACEMAKER="false" using sbd version 1.5.1+20211116.6bb085f-150400.1.5 pacemaker will not startup and crm status will report:

server01:~ # crm status
crm_mon: Error: cluster is not available on this node
ERROR: status: crm_mon (rc=102): Waiting for startup-trigger from SBD ...

Resolution

The issue is now fixed with sbd version 1.5.1+20221128.8ec8e01-150400.3.3.1

To workaround this problem for older sbd versions, SBD_SYNC_RESOURCE_STARTUP should be set to false.

Cause

The reason for this behaviour is the default value for SBD_SYNC_RESOURCE_STARTUP variable, which is "true".

When setting SBD_PACEMAKER="false" you need to explicitly set SBD_SYNC_RESOURCE_STARTUP="false"

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.