Network Management

RabbitMQ will not start on the primary after a failover to a secondary pool member

The issue is with the cluster configuration being broken and so this causes RabbitMQ issue on the Main Poller HA.

First published date

10/30/2018 6:33 PM

Last published date

3/22/2022 3:44 AM

Overview

In this scenario the RabbitMQ logs will show the following message:

Error description:

{error,{inconsistent_cluster,"Node rabbit@ServerName thinks it's clustered with node rabbit@ServerName2, but rabbit@ServerName2 disagrees"}}

This will prevent switching back to the Primary server from the Secondary.

Product section

Network Performance Monitor

Cause

Customer most likely has broken cluster configuration. That's why RabbitMQ on secondary could not start and has to be repaired after disabling the HA pool.

Resolution

To resolve the issue, complete steps from the "Troubleshoot the inconsistent_cluster error" section in Troubleshooting RabbitMQ.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.