Submit a ticketCall us

WebinarFREE IT Monitoring Webcast

Don’t miss out on our webcast, Essential IT Monitoring with SolarWinds ipMonitor, where we will show you how to keep an eye on your IT environment from one centralized, affordable, and lightweight monitoring tool: SolarWinds® ipMonitor®.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Some of the features of the polling engine not working after upgrade

Some of the features of the polling engine not working after upgrade

Table of contents
No headers

Issue:

After upgrading NPM to 10.5 the following functionalities are not working on the Primary and Additional Polling Engines:

 

  • Poll Now (nodes from APE)
  • List Resources (nodes from APE)
  • Weblauncher (on APE)
  • SWQL Studio on both servers targeting remote server
  • Installation of SAM 5.0.2 (on APE)


Cause:

The root cause of it was the fact that primary server was set with daylight saving time while secondary wasn't. So in reality the ZULU time on primary was 1 hour ahead.

 

Say for example:

  • request creation time - 15:25 (primary, where request was originating from)
  • current time - 14:26 (secondary, where request was targeted)


Resolution: 

 

  • After adjusting time settings, all features previously ending with errors (listed above) started to work perfectly.
  • In multi-polling engine environments all servers have to be set up with correct time with respect to Zulu time, not only having correct clock.
  • Co-ordinated Universal Time (UTC) zone is sometimes denoted by the letter Z. Since the NATO phonetic alphabet word for Z is "Zulu", UTC is sometimes known as Zulu time.
Last modified

Tags

Classifications

Public