Security Compliance

ARM - RabbitMQ service is failing to start

After migration from 8MAN to ARM or upgrade from previous versions, in some cases, it can happen that the RabbitMQ service cannot be started. The main hint to use this solution would be "schema_integrity_check_failed" error in the RabbitMQ logs.

First published date

4/9/2020 10:15 AM

Last published date

10/26/2021 10:37 AM

Overview

It has been observer that in some cases, after the upgrade from 8MAN to ARM or previous versions, RabbitMQ service is failing to start.
One of the reasons can be unsuccessful uninstall of older version RabbitMQ.
This will leave out the old folder which will cause the issue with starting the new version of RabbitMQ.

To make sure that user has this issue, you will need to check C:\ProgramData\SolarWinds\Orion\RabbitMQ\log folder and in logs files search for "schema_integrity_check_failed"

Product section

Access Rights Manager

Cause

The database schema has changed in this version of RabbitMQ. If you
attempt to start RabbitMQ-1.4.0 over top of a previous installation,
it will fail, citing "schema_integrity_check_failed".

Resolution

Follow these steps to resolve the issue:
 

  1. Stop ARM service
  2. Delete C:\ProgramData\SolarWinds\Orion\RabbitMQ\db\rabbit@NAME-OF-THE-ARM-SERVER-mnesia folder
  3. Restart ARM Service
  4. This process should recreate everything, and RabbitMQ will be started automatically in the process.