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 15
Situation
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
systemctl stop pacemaker ; OR crm cluster stopNote: 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
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com