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 > Network Performance Monitor (NPM) > Reboot alert does not trigger or send e-mail messages on nodes

Reboot alert does not trigger or send e-mail messages on nodes

Updated April 3, 2017

Overview

This article provides steps to resolve a reboot alert that stopped working, which is a known issue on NPM 12.x

Reboot alert no longer triggers or sends e-mail messages.

Environment

Orion Platform 2016.x and later versions

Resolution
1. Upgrade to NPM 12.1 and install OrionPlatform-v2017.1.5300-MSP-HotFix2

 

Workaround 1

  1. Perform a Remote Desktop Protocol (RDP) session to the Orion server.
  2. Go to C:\Windows\Temp\SolarWinds\JobEngine.v2.
  3. Check for stale data. All ShadowCopyCaches should show present timestamp.
  4. Delete all old ShadowCopyCache folders.
  5. Restart services for both Job Engine v1 and Job Engine v2.
  6. Perform a test reboot on a node to verify the reboot alert triggers.

 

Workaround 2

  1. Go to ORIONSERVERHOSTNAME/Orion/Admin/AdvancedConfiguration/Global.aspx
  2. Find "PubSubMaxQueueItemsCount" and set it to 0
  3. Click Save 
  4. Perform a test reboot on a node to verify the reboot alert triggers.

 

 

 

 

Last modified
12:42, 1 Jun 2017

Tags

Classifications

Public