# OS Linux Pacemaker Cluster Error Management Operating System (OS) clusters provide high availability and fault tolerance to critical applications and services in a distributed system. Among the various cluster management software available, Pacemaker stands out as a reliable and versatile tool for Linux-based systems. IT-Conductor allows users to automate error handling in a Pacemaker cluster environment. It can be applied to one or more systems and can be run manually or on a schedule. This feature is highly adaptable to any customer environment and can become an essential component of IT maintenance operations. ### Prerequisites * The system(s) should be registered in IT-Conductor for monitoring.

Figure 1: Linux System in IT-Conductor Service Grid

* A [Robot User](https://docs.itconductor.com/user-guide/account-administration/create-robot-users) should be created and associated with the application/DB/OS users with assigned roles/privileges to execute the local action on the system to be stopped/started.

Figure 2: Start/Stop Process Definitions

* The ownership of the process definition should be assigned to the [Robot User](https://docs.itconductor.com/user-guide/account-administration/create-robot-users). * The [Robot User](https://docs.itconductor.com/user-guide/account-administration/create-robot-users) should be able to view the following recovery definitions when navigating to **Management → Automation → Recover Definitions**. * Pacemaker: pcs resource failcount reset

Figure 3: Navigating to Recovery Definitions

{% hint style="info" %} **Note:** If the recovery definitions are not available for use, contact [IT-Conductor Support](https://docs.itconductor.com/references/support). {% endhint %} ### Automate OS Linux Pacemaker Cluster Error Management 1. Select the Linux system to implement the automation and click **Pacemaker Log**.

Figure 5: Pacemaker Log in IT-Conductor Service Grid

2. Click the **Threshold Overrides** icon.

Figure 6: Pacemaker Log Chart in IT-Conductor

3. Select the targeted override.

{% hint style="info" %} **Important:** Choose the override with the maintenance mode not enabled. {% endhint %} 4. Configure the threshold and define the desired schedule for running the automation.

Figure 8: Pacemaker Log Monitoring Configuratio Settings

5. Select the desired recovery action in the **Recovery** dropdown menu.

{% hint style="info" %} **Note:** If the recovery definitions are not available for use, contact [IT-Conductor Support](https://docs.itconductor.com/references/support). {% endhint %} 6. Configure to send a notification for this event. (Optional)

7. Click **Save** to complete the automation.

8. You can see the Automatic Cleaning Process of the OS Linux Pacemaker Cluster Error from the following view:

Figure 12: Automatic Cleaning of the OS Linux Pacemaker Cluster Error

### Related Information * [Clear Failed Fencing Actions Messages](https://www.suse.com/es-es/support/kb/doc/?id=000019463) * [Failed cluster actions in crm\_mon](https://www.suse.com/support/kb/doc/?id=000018057) * [How can I show and clear the fencing history in a Pacemaker cluster?](https://access.redhat.com/solutions/3761361) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.itconductor.com/user-guide/automation/os-linux-pacemaker-cluster-error-management.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.