Why stonith device fails to start/monitor with '-62 (Timer expired)' error when there is more than 64KB of output?

Solution In Progress - Updated -

Issue

  • Why when the verbose=1 is configured for fence_cisco_ucs it sometimes causes the monitor/start operation to timeout with the message below?

    Operation 'monitor' [xxx] for device 'test' returned: -62 (Timer expired)

  • Why the fence agent that outputs more than 64KB of data the stonith device fails to start/monitor the device?

Environment

  • Red Hat Enterprise Linux 7 with High Availability or Resilient Storage Add-on
  • paceamker-1.1.16-12.el7_4.7.x86_64, pacemaker-1.1.18-8.el7.x86_64
  • fence agents producing a lot of output such as:
    • fence_cisco_ucs in some environments with attribute verbose=1

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.