Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > Error: Time on NetFlow Receiver Service Above Threshold

Error: Time on NetFlow Receiver Service Above Threshold

Created by Brian O'Donovan, last modified by Brian O'Donovan on Jan 03, 2018

Views: 1,176 Votes: 2 Revisions: 4

Overview

This article provides brief information and steps to resolve the following error after changing the time on the Orion Server and FSDB server:

Time on NetFlow Receiver service [Orion] is 2/11/2016 10:20:10 AM. DB server time is: 2/11/2016 2:20:10 AM. The difference is: 28800.1s. Which is above critical threshold. The data won't be correct Synchronize the clocks and restart the service. 

 

Environment

All NTA versions

 

Cause 

The error is caused by the time difference between Orion Server and SQL Server.

In the error above, the time difference is 8 hours.

 

Resolution

The following are guidelines to avoid the issue:

  • Ensure that Orion, Flow Storage DB server and SQL server have the same time zone and time settings.
  • If you have additional pollers or additional web servers, these should also have the same time zone and time settings.
  • SolarWinds recommends to use NTP to synchronize time between servers.

 

 

 

 

Last modified

Tags

Classifications

Public