Resolution: A RabbitMQ node is inactive.

Content owner
Team	server-architects
Status	Pending
Last reviewed date
Rollout date

When to Use

Use this procedure when responding to a "A RabbitMQ node is inactive" alert notification.

Audience

Site services, Server support.

Prerequisites

Relativity System Admin access to view.

Procedures

Complete the following steps if Agent is unable to connect to RabbitMQ:

1. Verify the RabbitMQ server and/or cluster is running by logging into management UI and verifying each expected server is present and displaying as green under nodes. For more information, see RabbitMQ management UI.
2. On the Overview tab in the management UI, ensure RabbitMQ is listening on the expected ports:
   • amqp: 5672
   • amqp/ssl: 5671 (if configured for TLS, see Configure RabbitMQ For TLS )
   • http: 15672
   • https:15671 (if configured for TLS, see Configure RabbitMQ For TLS )
3. Verify RabbitMQ can be reached by navigating to the management page from the affected server(s).
4. Additionally, ensure the settings do not contain any trailing or leading whitespace, and ensure the casing matches for RabbitMQ's SharedAccessKey, SharedAccessKeyName, and ServiceNamespace settings.
5. Ensure the RabbitMQ user being used for authentication has full permission for the configured virtual host, see Configuring RabbitMQ