My Favorites

Close

Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

Pacemaker fails to start with 100 exit status

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

Environment

SUSE Linux Enterprise High Availability Extension 12
SUSE Linux Enterprise High Availability Extension 15

Situation

After Pacemaker cluster node is fenced, pacemaker.service unit fails with exit status 100.  Pacemaker starts up with no errors when issuing a manual restart.


Resolution

Edit the /etc/sysconfig/sbd file. 

Change SBD_DELAY_START parameter to "yes"

e.g.

SBD_DELAY_START="yes"

Alternate resolution:

Tweak sbd device msgwait timeout just shorter than the time it takes for SBD fencing action to complete and sbd.service to start up again after reboot.  Modify watchdog parameter to 50% of new msgwait timeout.  This is a process of optimization and must be tuned on a system-by-system basis.  For personalized SBD optimization assistance from a SUSE architect, professional consultancy is available through SUSE Professional Services.

Cause

If a node attempts to rejoin the cluster after it is fenced and before the msgwait timeout completes, pacemaker.service will fail to start with an exit status of 100.  Enabling the SBD_DELAY_START setting puts a "msgwait" delay on the startup of sbd.service.  While this will increase the time for the node to rejoin, it will ensure the node can rejoin without experiencing the msgwait conflict. This is more commonly seen in environments optimized for quick reboots, such as virtual and Public Cloud environments. 

Per SBD man page:

-4 N
Set msgwait timeout to N seconds.  This should be twice the watchdog timeout.
This is the time after which a message written to the node's slot will be
considered delivered.  (Or long enough for the node to detect that it needed
to self-fence)

Additional Information


See also:

Settings for long timeout in SBD_DELAY_START

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/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.

  • Document ID:7024009
  • Creation Date:16-JUL-19
  • Modified Date:16-JUL-19
    • SUSESUSE Linux Enterprise High Availability Extension
< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center