Network Management

No Reason of fail in SolarWinds High Availability Failover events

The article briefly guides you on what to do and where to look in an event; the Events widget lists no reason for failure.

First published date

12/9/2021 11:31 AM

Last published date

5/20/2025 6:42 PM

Overview


If an Events widget lists no reason for failure, please look at the appropriate logs. For example, if there is no reason for failure for an HA event, check High Availability logs to find the cause.
image.png

Product section

Orion Platform

Cause

This might be caused by timeouts, such as resource monitor timeout or RabbitMQ cluster facility timeout.

Resolution

To resolve the empty Reason of fail for events, check appropriate logs - HA logs for HA events, RabbitMQ logs for RabbitMQ events.

Time-outs can also be caused by external firewall settings that prevent both RabbitMQ cluster communication from stopping. This can lead to heartbeat issues, which trigger a failover.

By default, logs are located on the SolarWinds server in C:\ProgramData\SolarWinds\Logs.