An azure-lb resource fails with error "kill: (xxxx) - No such process" in a Pacemaker cluster

Solution In Progress - Updated -


  • An ocf:heartbeat:azure-lb resource agent fails its monitor operation with an error like the following:
Feb 22 15:56:34 node1 pacemaker-execd[1695]:  notice: nc_R16_ASCS_monitor_10000:85800:stderr [ /usr/lib/ocf/resource.d/heartbeat/azure-lb: line 92: kill: (2628) - No such process ]
  • An azure-lb resource fails every time I run a security scan.


  • Red Hat Enterprise Linux 7 (with the High Availability Add-on)
    • RHEL 7.4: resource-agents-3.9.5-105.el7_4.16 or later
    • RHEL 7.6: resource-agents-4.1.1-12.el7_6.28 or later
    • RHEL 7.7: resource-agents-4.1.1-30.el7_7.10 or later
    • RHEL 7.9: resource-agents-4.1.1-61.el7_9.4 or later
  • Red Hat Enterprise Linux 8 (with the High Availability Add-on)
    • RHEL 8.1: resource-agents-4.1.1-33.el8_1.4 or later
    • RHEL 8.2: resource-agents-4.1.1-44.el8_2.6 or later
    • RHEL 8.3: resource-agents-4.1.1-68.el8 or later

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