Why does my custom LSB or OCF resource fail a monitor action with return code 7 when the script doesn't have that exit code in my RHEL High Availability Pacemaker Cluster

Solution Unverified - Updated -

Issue

When the monitor action of an LSB or OCF resource fails, it exits with Return Code 7 even though the script doesn't have that return code built in:

Failed actions:
    custom_script_60000 on node1-priv 'not running' (7): call=337, status=complete, last-rc-change='Day Month 4 13:13:13 2015', queued=0ms, exec=24ms

Environment

  • Red Hat Enterprise Linux 6 with High Availability
  • Red Hat Enterprise Linux 7 with High Availability
  • Pacemaker

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.