Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Failover Engine (FoE) > Syslog or Trap Service fails to stop on a failover

Syslog or Trap Service fails to stop on a failover

Created by Justin Wyllys, last modified by MindTouch on Jun 23, 2016

Views: 960 Votes: 1 Revisions: 12

Overview

This article provides troubleshooting steps when the Syslog or Trap service fails to stop on a failover or switchover. 

Environment

  • FoE all versions

Cause

Unknown

Resolution

When a Syslog or Trap service  fails to stop on a failover or switchover, additional task in FoE needs to be created to force it to stop these services.

 

For Syslog services:

  1. Go to Applications > Tasks > Add
  2. Enter the following information:
    Name: Stop Syslog service
    Task Type: Pre Stop
    Command: TASKKILL /F /im SyslogService.exe
    Run as: local\SYSTEM (default)
  3. Click OK

 

For Trap services:

  1. Go to Applications > Tasks > Add
  2. Enter the following information:
    Name: Stop Trap service
    Task Type: Pre Stop
    Command: TASKKILL /F /im SWTrapService.exe
    Run as: local\SYSTEM (default)
  3. Click OK
Last modified

Tags

Classifications

Public