Network Management

Log Analyzer receives duplicate syslog messages

This article addresses an issue that causes a recently-configured load balancer to send duplicate syslog and trap messages to SolarWinds Log Analyzer.

First published date

4/12/2019 7:48 PM

Last published date

7/15/2022 7:23 AM

Overview

After you configure a load balancer to send syslog and trap messages to the SolarWinds Log Analyzer, formerly Log Manager for Orion, polling engines, Log Analyzer receives duplicate messages.

Product section

Log Analyzer

Cause

The load balancer sends Log Analyzer messages to an active High Availability (HA) server twice by mistake.

Each node is configured to send syslog and trap messages to two destinations: the active site, and the HA equivalent. Each site (active, inactive) should receive the syslog or trap once. In this situation, the active site receives a message twice when the load balancer should only send one message to each side of the HA pair.

Resolution

Set up your load balancer to only send syslog messages once to the HA Orion servers in the following configuration:

One message to the active HA server
One message to the inactive HA server (auto dropped as it is not active)

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.