Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > NetFlow Collector service is down after migrating the Orion database

NetFlow Collector service is down after migrating the Orion database

Updated June 27, 2017

Overview

This article describes an issue where the NetFlow Collector services are down but all NetFlow services are up after migrating the Orion database. The configuration wizard completes successfully on the NetFlow storage database and the charts display data.

The NTA business layer log displays the following error (C:\ProgramData\Solarwinds\Logs\NTA):

2017-06-02 10:04:43,117 [10] INFO  SolarWinds.Netflow.Processing.AppContext - Time on NetFlow Receiver Service [xxx xxx xxx ] is: 6/2/2017 10:04:43 AM. DB server time is: 6/2/2017 10:06:23 AM. The difference is: 100.8s. The thresholds are 60s for warning, 300s for error.

Environment

All NTA versions

Cause 

This issue is caused when there is a time difference of more than 300 seconds between the servers.

Resolution

Make sure that the Orion SQL server, main Orion polling engine, and the NetFlow storage database time are synchronized.

 

Last modified

Tags

Classifications

Public