Network Management

Syslog and trap service down after upgrade

Legacy syslog and trap services are not working in down status after NPM Orion has been upgraded

First published date

11/4/2019 5:04 PM

Last published date

6/10/2022 1:57 AM

Overview

This article goes over how to enable the legacy syslog and traps services that are stuck in down status after upgrading to Orion 2019.4

Error found in syslog log file:
INFO  SolarWinds.Orion.Common.SWEventLogging  The SolarWinds Traps Service is disabled by LegacyTrapServiceDisabled setting. Please check your configuration!
INFO  SolarWinds.Orion.Common.SWEventLogging - Solarwinds Trap Service Stopped
 
 

Product section

Network Performance Monitor

Cause

Due to continual improvement of the Orion platform, some legacy services have become disabled by default. If a user is not ready to move traps and syslogs over to the new service, they may enable the legacy traps in the advanced configuration options.

Note: This will not migrate the traps or syslogs over to the new trap viewer launched in Orion 2019.4

Resolution

  1. Log in to the Orion Web Console as an administrator and navigate to Advanced Configuration > Global. For example, http://localhost/Orion/Admin/AdvancedConfiguration/Global.aspx.
  2. Scroll down to the SolarWinds.Orion.Core.Common.Settings.LegacyServicesSettings section and clear the check boxes.


        3. Hit the save button at the bottom of the  screen.
        4. Orion services may need to be restarted in the Orion service manager or services.msc if they do not start on                  their own.

Traps and syslogs should now be working again.