'pcs resource restart' or 'crm_resource --restart' fails with "Error performing operation: Timer expired" in a RHEL 6 or 7 High Availability cluster with pacemaker

Solution Unverified - Updated -

Issue

  • When I run pcs resource restart without a --wait specified, the operation still times out and fails:
# pcs resource restart myResource-clone
Error: Could not complete shutdown of myResource-clone, 3 resources remaining
Error performing operation: Timer expired
Waiting for 3 resources to stop:
 * myFS-clone
 * myIPaddr-clone
 * myApp-clone
Deleted myResource-clone option: id=myResource-clone-meta_attributes-target-role name=target-role
  • Restarting a resource with pcs fails with a "Timer expired" error
  • Running crm_resource --restart fails with a timeout, even though I haven't specified -T or --timeout

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.