RabbitMQ timeout causes crashes.

Solution Verified - Updated -


  • RabbitMQ's default 5 second timeout doesn't match the 30 second timeout set for the resource in pacemaker.
  • In systems with high resource use this can create a situation where RabbitMQ fences itself but from the standpoint of Pacemaker the resource is up and running and there are no actions to correct the issue.


Red Hat Openstack Platform 7
Red Hat Openstack Platform 8
Red Hat Openstack Platform 9
Red Hat Openstack Platform 10

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