RabbitMQ failure with the error message "Node rabbit@[standby server] thinks it's clustered with node rabbit@[active server], but rabbit@[active server] disagrees"

This resolution works for many RabbitMQ issues on versions 2022.4 and newer. 

Below is an example of one: 
The Primary/Main Polling Engine of the Orion Platform / SolarWinds Platform utilizes RabbitMQ for some of the backend tasks. Upon starting the server or restarting Orion Services, RabbitMQ may not be able to start and remains in a stopped state. In the log (c:\ProgramData\SolarWinds\Orion\RabbitMQ\log\) you will find similar errors:

Error: {badmatch, 
     {error, 
      {{{function_clause, 
         [{rabbit_queue_index,journal_minus_segment1, ...

These steps may also resolve the error:

Node rabbit@[standby server] thinks it's clustered with node rabbit@[active server], but rabbit@[active server] disagrees

Use this approach if running rabbitmqctl.bat stop_app fails.

This issue occurs due to RabbitMQ is unable to parse the database because of a bad queue. 

1. On the Primary Polling Engine, open the "SolarWinds Platform Services Manager", AKA "Orion Service Manager" located by clicking on the Windows Start button > SolarWinds Platform > SolarWinds Platform Service Manager
   • 
2. Stop the RabbitMQ service.
   • 
3. You can either rename the following folder or copy it to a different location and deleted it:
   • C:\ProgramData\Solarwinds\Orion\RabbitMQ\db\
     • Example: Rename the "db" folder to "db{DATE}" (replace {DATE} with the actual date).
     • Or copy the "db" folder to the Desktop (or other desired location) and delete the "db"folder located at C:\ProgramData\Solarwinds\Orion\RabbitMQ\. 
4. Run the Configuration Wizard
5. When the wizard completes, the RabbitMQ service will start automatically.