Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

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: 45 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
19:30, 22 Jun 2016

Tags

Classifications

Public