Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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

Tags

Classifications

Public