RabbitMQ queues are experiencing crashes after upgrading to SolarWinds Platform versions 2024.4, 2024.4.1, and 2025.1

In 2024.4, 2024.4.1, or 2025.1, RabbitMQ queues to classic v2 from v1.  After this change, rabbitmq starts to crash after attempting to restarted crashed queues with the following crash dump in the log file (C:\ProgramData\SolarWinds\Orion\RabbitMQ\log\rabbit@SERVERNAME.log):

[error] <0.4133252.0>   crasher:
[error] <0.4133252.0>     initial call: rabbit_channel:init/1
[error] <0.4133252.0>     pid: <0.4133252.0>
[error] <0.4133252.0>     registered_name: []
[error] <0.4133252.0>     exception exit: {{{{badmatch,true},
[error] <0.4133252.0>                        [{rabbit_classic_queue_index_v2,init,3,
[error] <0.4133252.0>                             [{file,"rabbit_classic_queue_index_v2.erl"},
[error] <0.4133252.0>                              {line,183}]},

The symptoms are the following, but not limited to:

• Alerts are delayed or do not appear in a timely manner until a report occurs
• Consistent performance problems where RabbitMQ queues are slow to process messages
• RabbitMQ queues are not clearing and they are growing
• Traps are not creating alerts

There are some issues with the Classic v2 queues in some environments, causing it to crash. This is a known issue that impacts the following versions:

• SolarWinds Platform 2024.4
• SolarWinds Platform 2024.4.1
• SolarWinds Platform 2025.1

If you are unable to upgrade to this version, you can try the below workarounds:

Recommended Workaround: Revert queues to Classic v1 through command prompt

If you are using this workaround, upgrading to version 2025.1.1 is not strictly necessary. 

If you are on SolarWinds Platform 2024.1, then perform the below steps:

1. Revert to Classic Queues v1 by executing the command below in an administrative command prompt. 

"%ProgramFiles%\SolarWinds\Orion\RabbitMQ\sbin\rabbitmqctl.bat" set_policy orion-v1 ".*" "{\"ha-mode\":\"all\",\"ha-sync-mode\":\"automatic\",\"message-ttl\":86400000,\"expires\":86400000,\"queue-version\":1}" --priority 100 --apply-to queues

"%ProgramFiles%\SolarWinds\Orion\RabbitMQ\sbin\rabbitmqctl.bat" set_policy orion-shortliving-v1 "(.*@.*/w3wp_.*)|(.*_Database-Maint\.exe)" "{\"ha-mode\":\"all\",\"ha-sync-mode\":\"automatic\",\"message-ttl\":86400000,\"expires\":3600000,\"queue-version\":1}" --priority 110 --apply-to queues

net stop rabbitmq

rd "%ProgramData%\SolarWinds\Orion\RabbitMQ\db\rabbit@%COMPUTERNAME%-mnesia\msg_stores" /s /q

net start rabbitmq

2. Run the commands on the Primary Polling Engine with High Availability (HA) disabled or the pool removed. 
3. You can then run the commands on the HA standby. 
4. Restart all SolarWinds services on all polling engines and web servers. This will ensure that the queues have consumers correctly.

After running these commands, the queues will be Classic v1 and should no longer crash.

Alternate Workaround: Upgrade to 2025.1.1 to revert queues to Classic v1