Network Management

Trap/Syslog service shutting down automatically

This article overviews a potential solution for when your Trap Viewer / SysLog Services are not staying in a Running state after migrating your SolarWinds Application Server to a new Hostname/IP

First published date

11/2/2018 1:59 AM

Last published date

2/25/2022 12:57 AM

Overview

This article overviews a potential solution when your Trap Viewer / SysLog Services are not staying in a Running state after migrating your SolarWinds Application Server to a new Hostname/IP.

Product section

Orion Platform

Cause

This is due to the Centralized Licensing reading the first entry of the dbo.OrionServers table, which may reference your old application server.

You can verify what server has the license, by navigating to Settings -> All Settings in the Orion Web Console. Then click the "License Manager" at the bottom of the page. The App Server that the license is associated with will be listed here. If this is incorrect, follow the steps in the resolution below.

Resolution

Resolution A
1. Open Orion Database Manager.
2. Right click and select the [dbo].[OrionServers] table.
3. If the old server entry exists here, click the "Enable Table Editing" button, right click, and delete the row
    Note: A backup of this table may be a good idea in case you need to roll back any changes.
4. Restart Orion Services.
5. Check the License Manager page. The correct server should now be associated with the license.

Resolution B
1. Stop all the Orion services from the Orion Service Manager
2. Open the installer path C:\ProgramData\SoalrWinds\Installers
3. Right click on the Syslog/Trap installer (example: SYSLOGTRAPSLEGACY-X.X.X.XXXXX-SyslogTrapsInstaller.msi) then select the Repair option
4. Run the Configuration Wizard as administrator then select the ‘Service’ option only
5. Let the process finish without any issue