Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Error contacting poller

Error contacting poller

Updated

Overview

The following error appears when trying to add or assign nodes to another polling engine server:
The page at orionserver says:

Error contacting poller. An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.


 

On the Core.BusinessLayer.log, the following error is shown::

WARN  SolarWinds.Orion.Core.BusinessLayer.JobScheduler - Job Scheduler Exception:
System.ServiceModel.Security.MessageSecurityException: The security timestamp is invalid because its creation time ('2016-07-22T06:47:50.325Z') is in the future. Current time is '2016-07-22T06:41:30.664Z' and allowed clock skew is '00:05:00'.

Server stack trace: 
   at System.ServiceModel.Security.SecurityTimestamp.ValidateFreshness(TimeSpan timeToLive, TimeSpan allowedClockSkew)
   at System.ServiceModel.Security.SecurityTimestamp.ValidateRangeAndFreshness(TimeSpan timeToLive, TimeSpan allowedClockSkew)

Environment

Orion Core 2015.1.3 and later

Cause 

The current date/timestamp is invalid as it is set to a later future date.

Resolution

Make sure that all the Solarwinds Orion servers are synchronized to the same current time.

 

Last modified

Tags

Classifications

Public