Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > RabbitMQ will not start on the primary after a failover to a secondary pool member

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

Updated December 5, 2016

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.  

Environment

Orion Platform 2016.2 

Resolution

  1. Disable the HA pool.
  2. Shut down the secondary member of the pool.
  3. Reboot the primary member of the pool and wait for all services to become active.
  4. Power on the secondary member of the pool.
  5. Enable HA for the pool.

 

Last modified
17:18, 4 Dec 2016

Tags

Classifications

Public