SUSE Support

Here When You Need Us

Clear Pending Fencing Actions Messages

This document (000019816) 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

crm status print the following messages: 
 
Pending Fencing Actions:
* reboot of nfs-1 pending: client=pacemaker-controld.25747,
origin=nfs-2
* reboot of nfs-2 pending: client=stonith_admin.25666,
origin=nfs-1

 

Resolution

To cleanup these messages, pacemaker should be stopped on all cluster nodes at the same time via: 
systemctl stop pacemaker ; 
OR crm cluster stop 
Note: Above require downtime, since pacemaker should be stopped on all cluster nodes. 

After stopping pacemaker on all nodes, start it up using the following command: 
systemctl start pacemaker ; 
OR crm cluster start 

Pacemaker will cleanup failed messages during startup. 

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.

  • Document ID:000019816
  • Creation Date: 17-Dec-2020
  • Modified Date:11-Jul-2022
    • SUSE Linux Enterprise High Availability Extension

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

tick icon

SUSE Support Forums

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

tick icon

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.

tick icon

Open an Incident

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