A resource monitor operation fails with lrmd reporting "timed out after X ms" when the resource is otherwise expected to be running properly in a RHEL 6 or 7 High Availability cluster with pacemaker

Solution Unverified - Updated -

Issue

  • I'm seeing resource operations time out in my cluster, but the application seems to be running fine up until that point
  • Why did a monitor op timeout?
  • How can I diagnose monitor operation timeouts in my cluster?
Apr 29 10:43:59 node1.example.com lrmd[3598]: warning: rabbitmq-server_monitor_10000 process (PID 44052) timed out
Apr 29 10:43:59 node1.example.com lrmd[3598]: warning: rabbitmq-server_monitor_10000:44052 - timed out after 40000ms
Apr 29 10:43:59 node1.example.com crmd[3605]:   error: Operation rabbitmq-server_monitor_10000: Timed Out (node=node1, call=1682, timeout=40000ms)

Environment

  • Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add-On
  • 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.