Why do LVM monitor operations time out and fail with unknown error (1)?
Issue
- LVM resource monitor operations timeout with
unknown error (1) - These errors lead to fencing and failover with no indication of the problem
- Why is the error unknown?
- How can I determine what caused the error?
23:15:39 node01 lrmd[5774]: warning: imagedb-vg_monitor_10000 process (PID 2786) timed out
23:15:39 node01 lrmd[5774]: warning: imagedb-vg_monitor_10000:2786 - timed out after 30000ms
23:15:39 node01 crmd[5777]: error: Operation imagedb-vg_monitor_10000: Timed Out (node=node01.generic.cluster.com, call=239, timeout=30000ms)
23:15:39 node01 crmd[5777]: notice: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_FSA_INTERNAL origin=abort_transition_graph ]
23:15:39 node01 pengine[5776]: warning: Processing failed op monitor for logindb-vg on node02.generic.cluster.com: unknown error (1)
23:16:24 node01 pengine[5776]: warning: Node node01.generic.cluster.com will be fenced because of resource failure(s)
23:16:24 node01 pengine[5776]: warning: Scheduling Node node01.generic.cluster.com for STONITH
23:16:38 node01 stonith-ng[5773]: notice: Operation reboot of node02.generic.cluster.com by node03.generic.cluster.com for crmd.5777@node01.generic.cluster.com.ebb47d42: OK
Environment
- Red Hat Enterprise Linux (RHEL) 7 with the High Availability or Resilient Storage Add On
- LVM resource agent
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
