Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

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: 877 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