A fence_kdump stonith device fails to start and fencing fails in RHEL 6 or 7 pacemaker clusters

Solution Unverified - Updated -


  • How can I use fence_kdump with pacemaker on RHEL 6?
  • I have created a stonith device using fence_kdump, but pcs shows it as Stopped and shows a failure in trying to start it:
# pcs status 
Online: [ rhel6-node1-pcmk.example.com rhel6-node2-pcmk.example.com ]

Full list of resources:

 fs (ocf::heartbeat:Filesystem):    Started rhel6-node2-pcmk.example.com 
 kdump  (stonith:fence_kdump):  Stopped 

Failed actions:
    kdump_start_0 on rhel6-node1-pcmk.example.com 'unknown error' (1): call=31, status=Error, last-rc-change='Mon May  5 16:46:30 2014', queued=1011ms, exec=0ms
  • My fence_kdump stonith device is reporting errors in /var/log/messages:
May  5 16:46:31 rhel6-node1-pcmk stonith-ng[2136]:   notice: log_operation: Operation 'monitor' [2278] for device 'kdump' returned: -201 (Generic Pacemaker error)
May  5 16:46:31 rhel6-node1-pcmk stonith-ng[2136]:  warning: log_operation: kdump:2278 [ [error]: unsupported action 'monitor' ]


  • Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
  • pacemaker
  • fence-agents-kdump releases prior to 4.0.11-10.el7 in RHEL 7
  • fence-agents releases prior to 4.0.15-8.el6
  • fence_kdump in use as a stonith device fence agent
  • kdump/kexec configured and running on cluster nodes

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content