Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Netflow Traffic Analyzer (NTA) > 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: 4 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
20:33, 22 Jun 2016

Tags

Classifications

Public