Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > Flow Storage connection is lost after dropping packets

Flow Storage connection is lost after dropping packets

Created by Daniel Phillipps, last modified by MindTouch on Jun 23, 2016

Views: 804 Votes: 0 Revisions: 5

Overview

This article describes the issue about the Orion Server losing connectivity to flow storage server and new flows stop showing up in the Web Console with the followings errors in the logs:

2016-02-02 16:38:05,689 [Flow Listener on port 2055] WARN  SolarWinds.Netflow.Processing.PacketListener - Packet queue threshold reached. Dropping packets. Memory Used: 102400 KB
2016-02-02 16:38:06,001 [105] WARN  SolarWinds.Netflow.Processing.Workflow.NetFlowPacketWorkflowManager - Packet processing will suspend. Reason: flush queue size is 246 which exceeds threshold 246.
2016-02-02 16:38:06,001 [105] WARN  SolarWinds.Netflow.Processing.Workflow.NetFlowPacketWorkflowManager - Packet processing is suspended.
2016-02-02 16:38:06,203 [Flow Listener on port 2055] INFO  SolarWinds.Netflow.Processing.PacketListener - Resume receiving packets. Dropped 115988B of data, 85 packets.

Environment

NTA version 4.x

Cause 

This issue occurs due to a lost of connection between the Orion Server and flow Storage database.

Resolution

  1. Restart Flow Storage on the Flow Storage Server.
  2. Restart Netflow Service on the primary poller.
  3. Upgrade to NTA version 4.2.2.

 

Last modified

Tags

Classifications

Public