Why does a pacemaker resource appear to be using a different timeout value instead of the default timeout value?

Solution In Progress - Updated -

Issue

  • Why does a pacemaker resource appear to be using a different timeout value instead of the default timeout value?

    Apr 24 10:32:56 [10674] node42 lrmd: warning: child_timeout_callback: ping_monitor_5000 process (PID 481517) timed out
Apr 24 10:32:56 [10674] node42 lrmd: warning: operation_finished: ping_monitor_5000: 481517 - timed out after 20000ms

Environment

  • Red Hat Enterprise Linux Server (RHEL) 7 and 8
  • High Availability Add On
  • pacemaker

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content