Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > RabbitMQ messaging service stops communicating when the HA primary poller is offline

RabbitMQ messaging service stops communicating when the HA primary poller is offline

Updated 8-18-2016

Overview

You may have communication issues with the RabbitMQ messaging service on additional polling engines (APE) and additional web servers (AWS) with the High Availability primary main poller if: (1) the additional polling engine or additional web server services were running before HA was configured and have not been restarted AND (2) the primary main poller is offline (not just inactive).

 

The servers continue polling and updating the database, but do not connect to the main poller. To resolve, restart the Orion services on the additional polling engines and additional web servers. The RabbitMQ messaging service updates through the clients on the additional polling engines and additional web servers, communicating with the secondary main poller.

Environment

  • Orion 2016.2
  • High Availability
  • APE and AWS servers

Cause 

The RabbitMQ messaging service is managed by a client on additional polling engines and additional web servers. The service is configured to work with the main poller in the HA pool. You may encounter communication issues with RabbitMQ if (1) the additional polling engine or additional web server services were running before HA was configured and have not been restarted.  AND  (2) the primary main poller is offline, not just inactive.

Resolution

In the event of the main poller failing over to the secondary main poller and you have communication issues with RabbitMQ, restart all services on the additional polling engines and additional web servers. The restart configures the RabbitMQ messaging service client to point to the active main poller, reestablishing communications.

 
Last modified

Tags

Classifications

Public