A resource monitor operation fails with pacemaker cluster daemon reporting "timed out after X ms" when the resource is otherwise expected to be running properly in a RHEL High Availability cluster
Issue
- Resource operations are timing out in the cluster, but the application appears to be running fine up until that point
- Why did a monitor op timeout?
-
How to 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, 7, 8, 9 with the High Availability Add-On
pacemaker
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.